Related
Basically, due to a few of my friends having this phone and the lack of development here, I'm going to attempt to whip out a rom or two.
I plan to start with a stock rom, deodexed, zip aligned, optimized, bloatware removed, blur removed, ADW or GO launcher added..custom kernel..we'll see. I'd like to eventually port a few roms, but we really need a stable and legit Froyo rom to get anything stably ported.
At the moment, the only stock rom I have is a .SBF. Unfortunately I have no idea how to decompile this and the kitchen I plan to use won't do it either. I've tried ezxcodec, sbfcodec, and sbftool to open the file and none of which will work!
Currently I'm not around one of my friends with the phone, so I can't do this myself. We have some pretty bad weather conditions around here right now and I might not see him for a day or so.
So, what I need is a CLEAN nandroid. Preferably, fresh flash, root, nandroid..it would be great if you could run the optimizer script before nandroid also. As my testing time is somewhat limited since I don't have the device.
BUT please be sure this is a fresh flash with no sim card in or Google info ever entered...I don't want to accidentally get someone's private info.
Please send me a message if you can help me out and let's get the long over due development started.
Are you going to attempt to work with the Korean 2.2 ROM or the 2.1?
I think the 2.2 would be the one that would most benefit this community at this point. I know that the biggest piece to the Korean 2.2 ROM is that it does not work in the 1700/2100 Mhz range to allow US 3G service. Maybe this is something that you could help us to fix?
No matter what you end up doing, it is much appreciated.
I think I could knock out a nice 2.1 rather quickly, enough to hold people over while I work on a 2.2 rom. A cleaned up 2.1 would be much faster, better on battery, and still maintain stock functionality and stability..and would only take a little work to be released.
Has the radio issue been explored at all yet or is it still unknown to the cause? I could certainly work on Froyo, as a stable-ish 2.2 rom would lead to the ability to port other roms to the XT but I want to get a stable 2.1 out first.
The other problem is that I don't actually own the device, so testing is somewhat limited..
Either way, I need a nandroid before I can get started with anything because nothing seems to decompile these SBF files.. :-/
custom kernel? just curious how are you going to flash it in? are you aware that the bootloader is locked?
i've got a spare xt720 at home, i'll try to do a flash install and upload the nandroid when i have time.
Thank you.
Crap I forgot about the locked bootloader..I come from all HTC devices and forget about how locked down Moto is.
There is a thread already working on a custom kernel, which once completed could be baked into a rom and flashed with open recovery. However, since there's no source released, it's still in development..
Back to the locked bootloader tho, what additional limitations does this place on custom roms? I'm assuming it means no custom roms? Which would mean that unless someone manages to unlock the bootloader we're limited to only official Moto roms/leaks? I hadn't even fully considered that issue...
Sent from my HTC Glacier using XDA App
Ok so from my understanding, due to the locked bootloader, any rom built around a custom kernel can't be fully ported and retain all functionality unless its somehow piggy backed on the stock kernel.
So a modded stock rom would work fine then, right?
Once a working open source kernel is out, either for 2.1 or 2.2, at that point we can begin to modify it to work with different rom ports.
I'm going to continue research and hopefully will have a clean 2.1 out soon, so there will be something to play around with.
Sent from my HTC Glacier using XDA App
I will upload my nandroid later tonight for u. U can get the system.img from a link on navalynts abandoned thread if u wanna start now. The boot.img i uploaded was from 2.1 (im an idiot) so ill upload the right one later.
I looked thru that thread and couldn't find anything useful..I'd greatly appreciate it if you can upload the nandroid, I would like a full nandroid of 2.1 and the 2.2 leak if possible (the original 2.2 nandroid was pulled), as I'm currently unable to find a way to recompile the official SBF files from Moto. I won't be able to work on this till tonight tho, so no rush on anything.
Sent from my HTC Glacier using XDA App
On one of the last pages of the thread someone posted the link. Navalynt took down. It only contains system tho. Yea i work all day so it wont be till tonight grill i can post it.
Thanks man. Please do 2.1 first so we can get a stable/clean/fast rom out, then work on the Froyo issues, since it seems to be very buggy at the moment!
Hopefully will have a stable rom and a WIP rom ready by the weekend. Since testing is limited, it may take a little while longer than desired, but this forum knows how to wait lol..
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
Here is the system image from MY SGS 3, I thought one of our other devs might want to turn this into a ROM. I would do it, but I am a little swamped at the moment with after hours android dev work.
If someone has not taken a stab at it by the time I am back in here more "permanently", I will make my attempt at porting it over. You will need to grab a script that they use for CM, to grab the files off of your phone, also here is a good reference on porting as well.
SGS3 ROM to port:
http://www.androidfilehost.com/main/Motorola_ATRIX_2_Developers/jimbridgman/system.img.gz md5sum: 29a6c707d25520c28528b502bb190c7e
Porting guide, a very nice one at that:
http://forum.xda-developers.com/showthread.php?t=1512319
Have some fun.
jimbridgman said:
Here is the system image from MY SGS 3, I thought one of our other devs might want to turn this into a ROM. I would do it, but I am a little swamped at the moment with after hours android dev work.
If someone has not taken a stab at it by the time I am back in here more "permanently", I will make my attempt at porting it over. You will need to grab a script that they use for CM, to grab the files off of your phone, also here is a good reference on porting as well.
SGS3 ROM to port:
https://dl.dropbox.com/u/45576654/system.img
Porting guide, a very nice one at that:
http://forum.xda-developers.com/showthread.php?t=1512319
Have some fun.
Click to expand...
Click to collapse
I might take it on (you know me, that means I will try and fail and leave it dead most likely), but how the hell will we even get it to boot without at least an ics kernel? will we just have to wait until we get the update?
EDIT: i assume the gs3 is GSM correct?
lkrasner said:
I might take it on (you know me, that means I will try and fail and leave it dead most likely), but how the hell will we even get it to boot without at least an ics kernel? will we just have to wait until we get the update?
Click to expand...
Click to collapse
Try kexec, That is how the cyanogenmod team is "dual booting" for testing roms... who cares if it is just one proc for a test boot.... Once you can POC it with a 2.3.6 kernel, then you know you are on the right track, and can do a test flash. The only real issue you might have is that the source seems incomplete to me.
I know this because I tried to compile it and had all kinds of issues with missing pieces. I have successfully compiled two kernels that I am testing on my SGS 3 at the moment (one overclocked, the other under volted).
Just make sure you go and grab the arm-abi tool kit, this is the one I use, from
codesourcery:
http://www.mentor.com/embedded-software/codesourcery
All you need is the light version. It might take some work, but you may be able to merge the ICS kernel code (it is posted as a sticky higher up ^^^) with the MB/ME865 kernel to get what is missing. There are some how-tos out there to do it.
Yes the AT&T version is GSM(HSPA+)<E
Can you post the built in apps of sgs3 eg: s voice.
Sent from my MB865 using xda premium
kc92iyngr said:
Can you post the built in apps of sgs3 eg: s voice.
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
It is in the system.img file I posted.... just mount it as an iso and you can pull out /system/app and grab the Svoice.apk from there.
kc92iyngr said:
Can you post the built in apps of sgs3 eg: s voice.
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
I'll pull them out for you later today, I am about to tear this apart. it is downloading crazy slow though. I'm on an island in Vermont, so as you might imagine, my internet is not fantastic.
---------- Post added at 01:59 PM ---------- Previous post was at 01:46 PM ----------
jimbridgman said:
Try kexec, That is how the cyanogenmod team is "dual booting" for testing roms... who cares if it is just one proc for a test boot.... Once you can POC it with a 2.3.6 kernel, then you know you are on the right track, and can do a test flash. The only real issue you might have is that the source seems incomplete to me.
I know this because I tried to compile it and had all kinds of issues with missing pieces. I have successfully compiled two kernels that I am testing on my SGS 3 at the moment (one overclocked, the other under volted).
Just make sure you go and grab the arm-abi tool kit, this is the one I use, from
codesourcery:
http://www.mentor.com/embedded-software/codesourcery
All you need is the light version. It might take some work, but you may be able to merge the ICS kernel code (it is posted as a sticky higher up ^^^) with the MB/ME865 kernel to get what is missing. There are some how-tos out there to do it.
Yes the AT&T version is GSM(HSPA+)<E
Click to expand...
Click to collapse
Am I right that is SHOULD boot on a stock ICS kernel, like what came from that leak, if so, I can have someone that is running that test it out, and make sure the system is right, then I can build a kernel to run with kexec until we can get a real update.
I am new to porting and sort of to kernel building so tell me if this process sounds right for this.
1. fix up the gs3 system with our proprietary files -thats easy, I know how to do that
2. have someone that is running an ics kernel test it if possible
3. if that works it means I just need a stock ics kernel to run in kexec, which shouldn't be too hard because we should be able to use the me865 source and modify it to work with mb865. If it does not work, kernel building starts from scratch, which is were I will have to do some more research, and any help from you or others would be helpful.
My other question is how do we even load the new kernel with kexec? wouldn't we need this to boot first, then we can swap the kernel? Or is there a way to load up both at the same time?
I think I will set up a WIP thread for this if you don't mind. feel free to PM me if you don't want to post stuff here.
Thank you so much for all your help, and have fun with your new toy
lkrasner said:
I'll pull them out for you later today, I am about to tear this apart. it is downloading crazy slow though. I'm on an island in Vermont, so as you might imagine, my internet is not fantastic.
---------- Post added at 01:59 PM ---------- Previous post was at 01:46 PM ----------
Am I right that is SHOULD boot on a stock ICS kernel, like what came from that leak, if so, I can have someone that is running that test it out, and make sure the system is right, then I can build a kernel to run with kexec until we can get a real update.
I am new to porting and sort of to kernel building so tell me if this process sounds right for this.
1. fix up the gs3 system with our proprietary files -thats easy, I know how to do that
2. have someone that is running an ics kernel test it if possible
3. if that works it means I just need a stock ics kernel to run in kexec, which shouldn't be too hard because we should be able to use the me865 source and modify it to work with mb865. If it does not work, kernel building starts from scratch, which is were I will have to do some more research, and any help from you or others would be helpful.
My other question is how do we even load the new kernel with kexec? wouldn't we need this to boot first, then we can swap the kernel? Or is there a way to load up both at the same time?
I think I will set up a WIP thread for this if you don't mind. feel free to PM me if you don't want to post stuff here.
Thank you so much for all your help, and have fun with your new toy
Click to expand...
Click to collapse
Yeah I think that is a good start. Take a look at this link, the guys from team epic that do cyanogenmod ports have come up with a way to use kexec to test booting thier kernel and roms. You might PM one of them, I have not gotten to that point yet, plus these guys are working on the Sprint version, of the SGS3, but I am sure they can explain how they are doing this with kexec. These guys are on XDA, I have chatted with them on a couple issues I was having.
http://www.epiccm.org/
Oh, P.S.
Here is how to compile the "stock MB/ME865" kernel:
1. How to Build
- get Toolchain
From android git server , codesourcery and etc ..
- arm-eabi-4.4.3
- edit Makefile
edit "CROSS_COMPILE" to right toolchain path(You downloaded).
EX) CROSS_COMPILE= $(android platform directory you download)/android/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/arm-eabi-
Ex) CROSS_COMPILE=/usr/local/toolchain/arm-eabi-4.4.3/bin/arm-eabi- // check the location of toolchain
$ export ARCH=arm
$ make m2_att_defconfig
$ make
2. Output files
- Kernel : arch/arm/boot/zImage
- module : drivers/*/*.ko
3. How to Clean
$ make clean
Just make sure the toolkit is pointed to the install of the codesourcery toolkit I linked in the above post.
P.P.S
Your defconfig might be another pointer name, that you will have to find out for sure. You know the one above called m2_att_defconfig.
For the beginners don't try the rom,you might kill your phone!
I'd like to give this a try as well . Thanks a lot for all the help!
If/when we get this to work, do you think a JB port won't be too far behind? How big are the differences between stock ICS and JB kernels?
cogeary said:
I'd like to give this a try as well . Thanks a lot for all the help!
If/when we get this to work, do you think a JB port won't be too far behind? How big are the differences between stock ICS and JB kernels?
Click to expand...
Click to collapse
Glad to see you back around here, but lets not even give anything towards JB until we get ICS. if you are interested in helping with that, send me a PM, I have made some progress with cm9 (as in it boots fine, and i have some ideas for the radio).
cogeary said:
I'd like to give this a try as well . Thanks a lot for all the help!
If/when we get this to work, do you think a JB port won't be too far behind? How big are the differences between stock ICS and JB kernels?
Click to expand...
Click to collapse
Yay! Cogeary's back! Good to see you around again...
Sent from my phone's mind
cogeary said:
I'd like to give this a try as well . Thanks a lot for all the help!
If/when we get this to work, do you think a JB port won't be too far behind? How big are the differences between stock ICS and JB kernels?
Click to expand...
Click to collapse
ICS to JB is going to be a much smaller kernel jump, but there will be a HUGE performance increase due to project butter which is now officially part of Jelly Bean.
The key to running something like this is to get a kernel compiled and running with kexec, even though it is just 1 proc, it is a good way to get started. Ports will be much easier if you do some merging of the changed code in newer kernels and do merged kernel. There are instructions for doing a kernel that is merged from 2 sources to get a complete kernel.
Now this will just work for testing and porting, and the actual ICS or JB install from at least a leak will be needed to actually run the port, but you can get ahead of the game by doing what I have mentioned.
Well going to give this a go in a few days doing some maintenance on my computer but will get back with something (hope not a bricked phone) .....
(off topic ranting)
Hate to say it at this rate what getting close to a year since Ics release Jb might just be a pipe dream..... Think I am growing grey hairs waiting for something to give here..... Without bootloader unlock I feel so useless (Yea I could make a recovery image with all the bells and whistles but I got bigger plans).....
Downloaded so I could tinker with some files. Thanks for sharing.
Sent from my SAMSUNG-SGH-I997 using xda premium
Lol. Just my luck for the dropbox account to be temporarily shut down when my download's on 99%.
Well I guess I'll just sit here and wait. Unless anyone wants to be so kindly awesome enough to mirror it?
cogeary said:
Lol. Just my luck for the dropbox account to be temporarily shut down when my download's on 99%.
Well I guess I'll just sit here and wait. Unless anyone wants to be so kindly awesome enough to mirror it?
Click to expand...
Click to collapse
sure, no problem, give me a bit, my internet is slower than hell where I am right now.
EDIT: of course I didn't add it to dropbox originally, so now it is uploading to google drive. It just hit 1%
cogeary said:
Lol. Just my luck for the dropbox account to be temporarily shut down when my download's on 99%.
Well I guess I'll just sit here and wait. Unless anyone wants to be so kindly awesome enough to mirror it?
Click to expand...
Click to collapse
Yeah I got the dreaded e-mail from dropbox last night....
I will see what I can come up with for a hosting solution for this. I will update the OP once I have something.
cogeary said:
Lol. Just my luck for the dropbox account to be temporarily shut down when my download's on 99%.
Well I guess I'll just sit here and wait. Unless anyone wants to be so kindly awesome enough to mirror it?
Click to expand...
Click to collapse
I uploaded it to my Drive right away after downloading - try this for SGSIII ICS: https://docs.google.com/open?id=0B-CZ8hXV8qOiVGtjOHZ3ZEg5eFU
P.S. - I also have a JB dump there, if anyone's interested: https://docs.google.com/open?id=0B-CZ8hXV8qOiSkc3QkE1Y0ZsRkU
EDIT: make that 2 jelly beans: https://docs.google.com/open?id=0B-CZ8hXV8qOiS2QtcG41QUh4R1k
...I was pretty active during the I/O hype last week...
jimbridgman said:
Yeah I got the dreaded e-mail from dropbox last night....
I will see what I can come up with for a hosting solution for this. I will update the OP once I have something.
Click to expand...
Click to collapse
Why not try Filedropper or Mediafire?
MagicXB said:
Why not try Filedropper or Mediafire?
Click to expand...
Click to collapse
I am actually trying to get my recognized developer cert on here and get free premium access to xdafilehost, that all the recognized devs get access to.
We will see if I get it or not. If not I have other options, but things like filedropper will not do, I already looked into it
Hello everyone?
I posted a while back here if there was a possibility of seeing an AOKP port for this awesome device. but I got no answer from anyone
So I figured maybe its time to learn how to do it myself and contribute to the community here.
My question is where can I learn to start porting? It can't be rocket science. I've been observing the cm9 port for some time before the official ics was out. And it went from a non useable rom to a full daily driver in a few days after the release of the official ics. So I was thinking maybe we could get the same results with AOKP? I'm hoping someone can point me at the right direction that's all.
Thanks.
MacZzang said:
Hello everyone?
I posted a while back here if there was a possibility of seeing an AOKP port for this awesome device. but I got no answer from anyone
So I figured maybe its time to learn how to do it myself and contribute to the community here.
My question is where can I learn to start porting? It can't be rocket science. I've been observing the cm9 port for some time before the official ics was out. And it went from a non useable rom to a full daily driver in a few days after the release of the official ics. So I was thinking maybe we could get the same results with AOKP? I'm hoping someone can point me at the right direction that's all.
Thanks.
Click to expand...
Click to collapse
There are a lot of useful porting guides on the Chef Central sub forum on XDA. There's bound to be an AOKP guide there somewhere. Shouldn't be too hard considering we have CM9 mostly working thanks to locerra and aorth.
Sent from my SPH-L710 using xda premium
Thank you so much! I found a guide it should be what I'm looking for if u come across any other thread I would greatly appreciate it man. I'm gonna start this porting project soon. I just have a question if u have any experiance in this. What's the possible least damage that could come from this? I mean I've seen a few devs in the s2 section that hard bricked their phones testing out ports or something like that. Do u think that's possible? I'm definitely doing this, I just wanna know what might come my way. And thanks again
MacZzang said:
Thank you so much! I found a guide it should be what I'm looking for if u come across any other thread I would greatly appreciate it man. I'm gonna start this porting project soon. I just have a question if u have any experiance in this. What's the possible least damage that could come from this? I mean I've seen a few devs in the s2 section that hard bricked their phones testing out ports or something like that. Do u think that's possible? I'm definitely doing this, I just wanna know what might come my way. And thanks again
Click to expand...
Click to collapse
I have some experience with porting. And from what I've experienced, I've never had an actual "hard brick". I've done builds in which the device doesn't boot or boot loops but a clean Odin flash or backup usually fixes those soft bricks. I think the big thing to really worry about is the partition mounting bug that's been affecting galaxy devices with ICS. Those have been known to hard brick devices with seamlessly simple tasks, such as, using Odin, or even as flashing a ROM.
Sent from my SPH-L710 using xda premium
Ceelos09 said:
I have some experience with porting. And from what I've experienced, I've never had an actual "hard brick". I've done builds in which the device doesn't boot or boot loops but a clean Odin flash or backup usually fixes those soft bricks. I think the big thing to really worry about is the partition mounting bug that's been affecting galaxy devices with ICS. Those have been known to hard brick devices with seamlessly simple tasks, such as, using Odin, or even as flashing a ROM.
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
Hmmm it dose sound kinda scary... but what the hell I'm determined to get this done I've flashed maybe hundreds of roms to so many different devices, and I'm glad I never had any problems. I'm just a bit worried beacuse this is a rom I messed with and I'm not quite sure I'm any good at this yet seeing that htis is my first time ever messing around like this... Hay if it's alright with you, I would like to ask you a favor seeing that you have some experience in porting. I started the whole porting thing, and I followed a few guides here and there. I put together the rom but it hangs at the boot animation after about two mins...? give or take. I made a logcat and I was wondering if you could take a look at it if you don't mind I would greatly appreciate any input
thanks again!
Oh here's the link to the logcat
http://pastebin.com/10X2MWNw
MacZzang said:
Hmmm it dose sound kinda scary... but what the hell I'm determined to get this done I've flashed maybe hundreds of roms to so many different devices, and I'm glad I never had any problems. I'm just a bit worried beacuse this is a rom I messed with and I'm not quite sure I'm any good at this yet seeing that htis is my first time ever messing around like this... Hay if it's alright with you, I would like to ask you a favor seeing that you have some experience in porting. I started the whole porting thing, and I followed a few guides here and there. I put together the rom but it hangs at the boot animation after about two mins...? give or take. I made a logcat and I was wondering if you could take a look at it if you don't mind I would greatly appreciate any input
thanks again!
Oh here's the link to the logcat
http://pastebin.com/10X2MWNw
Click to expand...
Click to collapse
hmmmm...I *might* know whats causing the problem. Any way you can upload and link to the build you made?
Edit: I'm gonna get my environment set up and try building it. Its been a while.
Ceelos09 said:
hmmmm...I *might* know whats causing the problem. Any way you can upload and link to the build you made?
Edit: I'm gonna get my environment set up and try building it. Its been a while.
Click to expand...
Click to collapse
hmm where can I upload the file? should i like split the file into parts and email them? it would be around five parts.. or should i use one of these file hosting sites? so from what you see is it something big or is it a simple problem?
and again thank you so much
Edit: someone just looked at my logcat from the thread with the guide and said that it was a framework issue, here
E/JNIHelp ( 3712): RegisterNatives failed for 'com/android/server/PowerManagerService', aborting
F/libc ( 3712): Fatal signal 11 (SIGSEGV) at 0xdeadbaad (code=1)
could the problem be from the PowerManagerServise? ill try swapping that file and using the one from the base rom and see what happens
MacZzang said:
hmm where can I upload the file? should i like split the file into parts and email them? it would be around five parts.. or should i use one of these file hosting sites? so from what you see is it something big or is it a simple problem?
and again thank you so much
Edit: someone just looked at my logcat from the thread with the guide and said that it was a framework issue, here
E/JNIHelp ( 3712): RegisterNatives failed for 'com/android/server/PowerManagerService', aborting
F/libc ( 3712): Fatal signal 11 (SIGSEGV) at 0xdeadbaad (code=1)
could the problem be from the PowerManagerServise? ill try swapping that file and using the one from the base rom and see what happens
Click to expand...
Click to collapse
Hold off on uploading it, I'll try n compile a build myself within the next couple days. As for the error which libandroid_runtime.so were u using? If u were using the base one, try replacing it with the CM one. I'll have to take a closer look at the log later
Edit: Should have all my build environment and sources synced sometime around mid-week, at the latest. Had to juggle some partitions around and reinstall Linux. Any progress on your end lately?
Sent from my SPH-L710 using xda premium
Ceelos09 said:
Hold off on uploading it, I'll try n compile a build myself within the next couple days. As for the error which libandroid_runtime.so were u using? If u were using the base one, try replacing it with the CM one. I'll have to take a closer look at the log later
Edit: Should have all my build environment and sources synced sometime around mid-week, at the latest. Had to juggle some partitions around and reinstall Linux. Any progress on your end lately?
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
well I'm not any good at linux or and kinda programming sadly but I've been trying different galaxy s2 roms ive tried swapping around hundreds of different files but to no prevail .. I cant get passed the boot screen. I've done numerous logcats and they all seem to have the same error... but the number after the F/libc keeps changing... is there anything i should learn so that I can be of real help? besides just swapping files
MacZzang said:
well I'm not any good at linux or and kinda programming sadly but I've been trying different galaxy s2 roms ive tried swapping around hundreds of different files but to no prevail .. I cant get passed the boot screen. I've done numerous logcats and they all seem to have the same error... but the number after the F/libc keeps changing... is there anything i should learn so that I can be of real help? besides just swapping files
Click to expand...
Click to collapse
I've tried compiling it from source but get an error when trying to compile the kernel. I'm looking into it right now. Just seems to be missing some base files.
Also, by Galaxy S2 ROMs you mean AOKP based ROMs, right? As far as I know, in order to understand and fix most issues you'll need to learn some C programming, along with some python. Porting with wizip requires just a basic understanding of the Android files. (framework, libs, etc.) a user named xboxfanj has ported alot of ROMs, you can ask him for some insight. Marcusant is another user whose ported a lot as well, but they easily have more insight in this than I do.
Edit: asked xboxfanj for some insight, here's what I got:
"What did you do to port this? The method I recommend is first delete everything in the aokp zip besides the system folder and then copy everything besides system from cm to aokp. Then copy the tab's system/build.prop and etc and vendor and firmware (if there is a folder for that) folders. Also copy the lib/hw and lib/egl folders from cm to aokp. I'm not sure if you're talking about the galaxy tab 2 7" or the original galaxy tab, but either way, go to github.com/themuppets/proprietary_vendor_samsung
If you have the original gtab, go to the p1 and p1 common folders. If you have the new one, go to p31xx in the common folder. You can download it as a zip by clicking zip on the webpage. Then you can just drag and drop the files. After that, copy bin/rild bin/pppd (if its there) lib/libril lib/libsec-ril and lib/libsecril-client. I recommend porting from the kindle fire if you have the tab 2 7" since that device has the same resolution.
Not much is given away by your original logcat. Maybe try a different libandroidruntime (if you were using your cm one, use the aokp one, if you were using the aokp one, use the cm one).
Another method you could use is copy app, framework, and media from the aokp zip to the cm zip (delete those folders from cm first)."
Sent from my SPH-L710 using xda premium
Ceelos09 said:
I've tried compiling it from source but get an error when trying to compile the kernel. I'm looking into it right now. Just seems to be missing some base files.
Also, by Galaxy S2 ROMs you mean AOKP based ROMs, right? As far as I know, in order to understand and fix most issues you'll need to learn some C programming, along with some python. Porting with wizip requires just a basic understanding of the Android files. (framework, libs, etc.) a user named xboxfanj has ported alot of ROMs, you can ask him for some insight. Marcusant is another user whose ported a lot as well, but they easily have more insight in this than I do.
Edit: asked xboxfanj for some insight, here's what u got:
"What did you do to port this? The method I recommend is first delete everything in the aokp zip besides the system folder and then copy everything besides system from cm to aokp. Then copy the tab's system/build.prop and etc and vendor and firmware (if there is a folder for that) folders. Also copy the lib/hw and lib/egl folders from cm to aokp. I'm not sure if you're talking about the galaxy tab 2 7" or the original galaxy tab, but either way, go to github.com/themuppets/proprietary_vendor_samsung
If you have the original gtab, go to the p1 and p1 common folders. If you have the new one, go to p31xx in the common folder. You can download it as a zip by clicking zip on the webpage. Then you can just drag and drop the files. After that, copy bin/rild bin/pppd (if its there) lib/libril lib/libsec-ril and lib/libsecril-client. I recommend porting from the kindle fire if you have the tab 2 7" since that device has the same resolution.
Not much is given away by your original logcat. Maybe try a different libandroidruntime (if you were using your cm one, use the aokp one, if you were using the aokp one, use the cm one).
Another method you could use is copy app, framework, and media from the aokp zip to the cm zip (delete those folders from cm first)."
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
Ok I've downloaded a bunch of different roms for a number of devices (nexus S, galaxy s2, galaxy s, galaxy tab p1,s2 at&t, tab 2 7.0) but this time they are all pure AOKP builds not that they weren't before but they were all custom. I'm gonna try out the two methods you just mentioned and see what happens. ill try to reach Marcusant sense you already reached xboxfanj. I'll try to start learning some C and python and hopefully i can learn enough in time to actually be able to do something here. so what do you do for a living man are you a programmer?
MacZzang said:
Ok I've downloaded a bunch of different roms for a number of devices (nexus S, galaxy s2, galaxy s, galaxy tab p1,s2 at&t, tab 2 7.0) but this time they are all pure AOKP builds not that they weren't before but they were all custom. I'm gonna try out the two methods you just mentioned and see what happens. ill try to reach Marcusant sense you already reached xboxfanj. I'll try to start learning some C and python and hopefully i can learn enough in time to actually be able to do something here. so what do you do for a living man are you a programmer?
Click to expand...
Click to collapse
You might wanna port mainly from the Galaxy S2, seeing as how we have more in common with them hardware wise.
And no. I'm about to start my college classes next month at DeVry. Gonna do their Computer Engineering course. I don't know much but as soon as class kicks in, I'm hoping it'll kick start my development here on XDA. For the time being, I usually lurk around n help. Maybe learn a thing or two by reading a random thread or guide.
Sent from my SPH-L710 using xda premium
Well things don't look so good from my end... I've put together about 16 different roms and they all won't go past the boot screen. And the galaxy s2 roms kept giving me the same fatal error... I'm hitting a wall here I don't know what to do.. I'm guessing we just have to get our hands dirty with this one.. I'm doing some reading on python and c hopefully I can figure this out...
So ur a student? That's cool I wanted to learn program and computer engineering before I got into university
Sweet God Almighty, if we got AOKP on this thing I... I... well... I think I might just cry for joy. :crying:
Hahahaha yeah same here I love AOKP based roms, they have more options! And aokp has a unicorn! But sadly we have been trying here for a few days and well I'm not really a Dec I'm just following porting guides and tutorials around xda trying out different things here and there hoping we can get passed the boot screen. Would definitely appreciate your help
Been having some trouble setting my build environment up, so I'm currently seeking some help from others who have experience building AOKP from source. Hopefully they can guide me through it and I find what I did wrong
Sent from my SPH-L710 using xda premium
AOKP == CM
Android Open Kang Project is basically CyanogenMod. Minus some features. I have no interest in seeing AOKP on this device. Sorry. Any optimizations AOKP could bring would already be in CM.
For what it's worth, I did get a device tree configured which can build AOKP, but it didn't boot (stuck at boot animation, logs complaining about yamaha audio). That was in July, and I never went back to it.
aorth said:
Android Open Kang Project is basically CyanogenMod. Minus some features. I have no interest in seeing AOKP on this device. Sorry. Any optimizations AOKP could bring would already be in CM.
For what it's worth, I did get a device tree configured which can build AOKP, but it didn't boot (stuck at boot animation, logs complaining about yamaha audio). That was in July, and I never went back to it.
Click to expand...
Click to collapse
I figured you wouldn't be interested aorth I don't blame you. I have little experience in this and figured I'd hop in and see if I could do get it going but the Yamaha audio issue seems to come up in every logcat I take as well.
Sent from my SPH-L710 using xda premium
aorth said:
Android Open Kang Project is basically CyanogenMod. Minus some features. I have no interest in seeing AOKP on this device. Sorry. Any optimizations AOKP could bring would already be in CM.
For what it's worth, I did get a device tree configured which can build AOKP, but it didn't boot (stuck at boot animation, logs complaining about yamaha audio). That was in July, and I never went back to it.
Click to expand...
Click to collapse
Aorth u broke my heart man I actually had lots of hope that this can be pulled off... so you're saying this is impossible to do? I like aokp because if the rom control menu I feel it has more options and customization. But cm9 is great too. Thank you so much for all the hard work u have put into bringing cm9 to our awesome tabs
Ceelos09 said:
I figured you wouldn't be interested aorth I don't blame you. I have little experience in this and figured I'd hop in and see if I could do get it going but the Yamaha audio issue seems to come up in every logcat I take as well.
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
Yeah I saw the Yamaha audio thingie too...? What's the problem? Is that a driver thing or something else? From the way you both mentioned it I'm guessing its something serious.. ?
Sent from my GT-P6200 using xda premium
aorth said:
Android Open Kang Project is basically CyanogenMod. Minus some features. I have no interest in seeing AOKP on this device. Sorry. Any optimizations AOKP could bring would already be in CM.
For what it's worth, I did get a device tree configured which can build AOKP, but it didn't boot (stuck at boot animation, logs complaining about yamaha audio). That was in July, and I never went back to it.
Click to expand...
Click to collapse
Curious, what can CM do feature wise that AOKP can't?
I can think of quite a few that AOKP can do that CM can't.
Posted from my Galaxy S III.
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.