Database Info

[ROM] ICS system image from AT&T SGS 3 (SGH-I747) version 4.0.4

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+)&LTE

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+)&LTE
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

Why an official CM 10 is not possible for Atrix 2?

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.

[ROM][4.3] Unofficial OmniROM builds for Nexus 7 (grouper) [MULTIWINDOW][16/10]

OmniROM Unofficial Builds
As you all know, OmniROM has been announced yesterday. This brand new ROM contains a lot of new, exciting functionality. One of these new functions is the multi-window support! Just like ROMs on some Galaxy Notes, or the ancient Cornerstone, you can run two applications simultaneously! Aside from that, the best thing about this ROM is the focus on the community: while the ROM itself is not available yet, the developers behind it really seem to be willing to listen to the community, which is a really good thing.
As the team of OmniROM states on their website:
Omni is what custom ROMs used to be about – innovation, new features, transparency, community, and freedom. We offer you an alternative to other ROMs that may choose to water down their distribution at the expense of providing options for the user.
Click to expand...
Click to collapse
And the list of features as listed by XpLoDWilD in this topic:
Flippable Quick Settings
Roadrunner mode
Multi-window(!)
Daydream enhancements
Integrated Performance Control
Multi-workspace
Color-changeable, 3D depth Phase Beam
And a bunch more
Click to expand...
Click to collapse
Unofficial builds
However, builds are not available yet. Logically, the ROM probably has not been thoroughly tested yet and that's why they are not building their source on a nightly basis. If you are as impatient as I am, you probably want to get your hands on this ROM as soon as possible! That's why I compiled OmniROM from source, for the Nexus 7 (grouper).
This flashable ZIP has not been tested yet by myself, but it should be OK. Compiled on Ubuntu 13.04 x86_64, completely as-is from the repository of OmniROM. Let me say again that this ROM is not modified by me; it is directly compiled from source and packaged into a ZIP. All credits go to the team behind OmniROM at http://omnirom.org.
Downloads
The builds below will probably be updated about every three days. I recompile from source whenever significant modifications are added to the multi-window functionality.
16/10 (working fine, with multi-window)
custom_grouper-ota-eng.chaoszx.zip (145.9 MB)
https://mega.co.nz/#!yEsHkDSa!PtTVqVPcvFY3FqP20M-1Vnq87rkVMPKJJ4aPuJA0IH8
14/10 (does not boot):
omnirom-4.3-20131014-NIGHTLY-grouper-unofficial.zip (138.7 MB)
https://mega.co.nz/#!HVF3DDAY!FveJvAE2Wffm2WNcezemTAwHYAleOKf13-zg82cZ118
Thank you
If you appreciate the time I spend to compile these ROMs from source for you, a donation would be appreciated as it would cover a bit of my expenses on power. Aside from that, I am hoping to save some money before I go to university next year, so any donation is much appreciated! PayPal donations can be sent to [email protected]. Thank you in advance for your support.
Notes
Multi-window can be activated by opening an app. Then go back to the launcher by pressing Home. Load up another app. Press the Multitask button, long-press the app you opened previously, and hit 'Split View'.
The Back button is not working at boot. To fix it, go to Settings > Language and Input > Default (under Keyboard & Input Methods) > Google Keyboard. The force closes of the AOSP keyboard won't happen now, and your Back button will work fine.

Reserved.

Reserved as well.

Flashing failed :/ Will try again.

Hypercaine said:
Flashing failed :/ Will try again.
Click to expand...
Click to collapse
Hang on, I am about to flash it on my Nexus 7. If it doesn't flash, I'll check what's wrong and fix it within an hour

Flashing right now, this is gonna be great!
Sent from my SCH-I535 using xda app-developers app

FAILED
set_perm: some changes failed
E:Error executing updater binary in zip ´/sdcard/
Error flashing zip
Same problem here

Confirmed that there is something wrong. Hang in there guys, working on a solution as we speak

chaosz-x said:
confirmed that there is something wrong. Hang in there guys, working on a solution as we speak
Click to expand...
Click to collapse
f5...f5...f5...f5...f5...f5...f5...f5...f5...f5...f5...f5...f5...f5...f5...f5...f5...f5...

The issue with the flashing is resolved. Before uploading the new ZIP, I am investigating the ROM itself. Check back in about an hour at least

Eagerly waiting
Sent from my Nexus 7 using XDA Premium HD app

Chaosz-X said:
Check back in about an hour at least
Click to expand...
Click to collapse
This looks suspiciously like an ETA, if I ever saw one...

When installing, flashing failed. Also, upload to a site that is android-friendly? Mega is hard for me to use. Maybe mediafire?

Failed for me also.
Sent from my SCH-I545 using Tapatalk now Free

flash fails because it says tilapia,mako,flo/deb.........no grouper is mentioned

podagee said:
flash fails because it says tilapia,mako,flo/deb.........no grouper is mentioned
Click to expand...
Click to collapse
I take it you get a set_perm (status 7 error)? This has to do with the updater script trying to give permissions to a file that doesn't exist, it is relatively easy to resolve. I'll take a look once I get home. BTW, tilapia, mako and flo are probably officially supported, which is why they are mentioned, as this is an unofficial build, it isn't (yet) mentioned
Sent from my Nexus 7 using xda app-developers app

Grouper is mentioned in the post of OmniROM, Grouper is available in the device tree of OmniROM, and this build is meant for Grouper.
The ZIP has been corrected to flash correctly. It was doing some set_perms on non-existing files. Those issues have been resolved now. However, the ROM fails to boot for some reason. I don't know why it is not booting as this is a completely unmodified build. I am going to sync the repository again now and do a new build. This afternoon I'll have a new build to try.

Chaosz-X said:
Grouper is mentioned in the post of OmniROM, Grouper is available in the device tree of OmniROM, and this build is meant for Grouper.
The ZIP has been corrected to flash correctly. It was doing some set_perms on non-existing files. Those issues have been resolved now. However, the ROM fails to boot for some reason. I don't know why it is not booting as this is a completely unmodified build. I am going to sync the repository again now and do a new build. This afternoon I'll have a new build to try.
Click to expand...
Click to collapse
FWIW I'm having the exact same problem with my build....it won't boot. Using sources synced as of yesterday morning.
I'm also re-syncing to see if that helps.

Thank you for your efforts! Waiting to try it

God I hate this new ADB system in Jelly Bean. Only allows a logcat if you grant access through Android itself. But when your device doesn't boot, it is impossible to get live logcats atm. Still working on a fix and progress is being made though

TWRP 2.7 for HTC Desire S

Hi. As you propably know, there is no TWRP 2.7 for saga. This is why:
Saga would need a number of updates in order to make it work with 4.4 Kit Kat ROMs. 4.4 ROM support really doesn't depend on the recovery itself. The kernel and other parts of the ramdisk have to support SELinux contexts in order for the set_metadata functions to work. I don't have a saga myself and at this point I have no plans to continue to support the device. I've been building saga in a CM7 / gingerbread tree which doesn't support the things needed for SELinux. The device would need to be compiled with an updated kernel in at least a 4.1 and preferably a 4.3 or 4.4 tree to support installing Kit Kat ROMs.
I plan to drop official support for any device that I've been building in ICS or Gingerbread trees which includes saga. If people want to see continued support for those devices, then hopefully developers for those devices will step up and build TWRP themselves and maybe offer their updated device files to us so that we can extend official support.
Click to expand...
Click to collapse
So basically we need developers who would like to help with that. I'm not that techy to understand what the problem is but I would like you to tell me and help.
BTW! Why our device is not available in DevDB! How do we change that?

Hm. I might take a shot at this. Though I personally prefer 4ext

devil-kin said:
Hm. I might take a shot at this. Though I personally prefer 4ext
Click to expand...
Click to collapse
It would be really splendid thing to do sir

Got it to build, just not to boot. I guess a black screen is no use to anyone
Will fiddle some more with it.

devil-kin said:
Got it to build, just not to boot. I guess a black screen is no use to anyone
Will fiddle some more with it.
Click to expand...
Click to collapse
That's great! It would be even better if you could somehow share some of your work here so maybe someone else could take a look (i don't know if it's possible. But you use github right?) I would love to add this project to DevDB but it seems that our phone is not there and i don't know how to add it.

My github repos are at https://github.com/jdeluyck - I haven't uploaded anything yet save for the changes to the repo file to pull in TWRP.

Here ya go, first build of TWRP 2.7.0.0 for Desire S, which seems to work
Please test and let me know

PERFECT!
devil-kin said:
Here ya go, first build of TWRP 2.7.0.0 for Desire S, which seems to work
Please test and let me know
Click to expand...
Click to collapse
I flashed it, I backed up my rom, I wiped, I flashed my rom clean, it booted, I went to recovery and I restored my rom. Everything went perfect, no problems whatsoever! Now there are 2 questions left to ask.
1. May I update TWRP for saga developement thread and attach this build?
2. Would you be willing to offer updated device files to TWRP team? From my observation most people download TWRP drom official website and it would be great if 2.7 would make an appearance there.
Anyway great work devil-kin :highfive: Personally I see TWRP as the best recovery and I'm on it from 2.2. Seeing it still working in its latest iteration on my beloved DS makes little tears appear in the corners of my eyes. I absolutely love this phone for it's size, specs, build quality and weird survability (many screen to sidewalk encounters and no broken glass Only praiseworthy scars). LONG LIVE DS! <3

VnnAmed said:
1. May I update TWRP for saga developement thread and attach this build?
Click to expand...
Click to collapse
Sure. I'm even willing to offer up new updates as long as I got a working CM tree to base it off.
VnnAmed said:
2. Would you be willing to offer updated device files to TWRP team? From my observation most people download TWRP drom official website and it would be great if 2.7 would make an appearance there.
Click to expand...
Click to collapse
Sure - the device files can be found at https://github.com/jdeluyck/android_device_htc_saga
Do I have to send them to anyone specific?

devil-kin said:
Sure. I'm even willing to offer up new updates as long as I got a working CM tree to base it off.
Sure - the device files can be found at https://github.com/jdeluyck/android_device_htc_saga
Do I have to send them to anyone specific?
Click to expand...
Click to collapse
Thank you very much If you could, i would like you to PM Dees_Troy and tell him that you have succesfully compiled 2.7 for saga, so if he has some more technical questions you can answer them I'm updating TWRP for saga thread right away

Custom Roms (Lineage etc)

Ahoi,
the guys from f(x)tec said they would send out some devices to developers of custom roms including lineage to help development of the rom. Did this already happen? Do lineage devs have the phone and did they start porting? Just curious if that happens at all. I'm hoping to put lineage on mine asap.

There are few developers who are making Lineage OS and Sailfish OS for Pro1. Chen showed some alpha build on Twitter previously. Also, devs has the source code since last month.
https://mobile.twitter.com/chenliangchen/status/1148357734204616704
https://mobile.twitter.com/tdmcode/status/1180553338389028865
http://talk.maemo.org/showpost.php?p=1560008&postcount=2235
chen said:
What I can confirm is that there are 2 senior developers has been working on Lineage OS since a while ago. And they've made some great progress. (All the credit goes to them)
They are awaiting for the official release and can move the porting project into the next stage I believe.
That's as far as I know, and again, it's a great work of Lineage community.
PS: When I tried to flash SFOS initial release onto Pro1 I need to flash a custom TWRP, which is I believe also from Lineage OS devs.
Click to expand...
Click to collapse

https://github.com/tdm?tab=repositories
With the email today confirming those who are in the first batch, we're getting close! What I think would be really nice would be working TWRP so can make stock backup on day zero. And of course for root, los, or sfos...

enigma9o7 said:
https://github.com/tdm?tab=repositories
With the email today confirming those who are in the first batch, we're getting close! What I think would be really nice would be working TWRP so can make stock backup on day zero. And of course for root, los, or sfos...
Click to expand...
Click to collapse
As a member of the proto guys, I can assure you that the fastboot images will get released quickly. We have the shipping firmware, maybe there'll be simply a website for that. A working TWRP exists, but keep in mind system-as-root limitations.

j1505243 said:
A working TWRP exists, but keep in mind system-as-root limitations.
Click to expand...
Click to collapse
Does backup work now? I'd heard the earliest port worked for flash but not backup.
Any chance you can share? I expect my phone any day now...

enigma9o7 said:
Does backup work now? I'd heard the earliest port worked for flash but not backup.
Any chance you can share? I expect my phone any day now...
Click to expand...
Click to collapse
Backups require decryption support, but since it's a stock msm8998 platform you can expect that rather quickly. Sharing is what I'll leave to the original creators, we're informed about the shipment progress.

j1505243 said:
keep in mind system-as-root limitations.
Click to expand...
Click to collapse
Don't suppose you have a link that could explain this to people who have no idea what you mean?
I think this has something to do with the fact that even as root in Android if you modify stuff in /system it doesn't stick after reboot. But I'm really only guessing and haven't bothered to read up on it yet.

enigma9o7 said:
Don't suppose you have a link that could explain this to people who have no idea what you mean?
I think this has something to do with the fact that even as root in Android if you modify stuff in /system it doesn't stick after reboot. But I'm really only guessing and haven't bothered to read up on it yet.
Click to expand...
Click to collapse
System-as-root means that /system is mounted as /, but it also means that recovery is a part of boot image, so flashing it as the whole boot partition won't let you boot the system. There'll be a need for TWRP installer script.

enigma9o7 said:
Don't suppose you have a link that could explain this to people who have no idea what you mean?
I think this has something to do with the fact that even as root in Android if you modify stuff in /system it doesn't stick after reboot. But I'm really only guessing and haven't bothered to read up on it yet.
Click to expand...
Click to collapse
https://source.android.com/devices/bootloader/system-as-root

https://twitter.com/tdmcode/status/1197945254906777600

Test builds are available:
- http://files.nwwn.com/android/pro1/lineage.html

Initial impressions?
Flash-A-Holic said:
Test builds are available
Click to expand...
Click to collapse
Thanks for posting this. I've been unable to find any impressions as to the stability of these ROMs. Yes, they are testing roms, but IME there are testing roms and then there are testing roms.
Are these the former (unsupported but mostly stable) or the latter (you don't want any of your real data on it, will crash at random times and missing core functionality)?

maplesteel said:
Thanks for posting this. I've been unable to find any impressions as to the stability of these ROMs. Yes, they are testing roms, but IME there are testing roms and then there are testing roms.
Are these the former (unsupported but mostly stable) or the latter (you don't want any of your real data on it, will crash at random times and missing core functionality)?
Click to expand...
Click to collapse
It's been stable for some time now. I'll be posting a thread here in the next day or two and making lineage official in the next week or two.

tdm said:
It's been stable for some time now. I'll be posting a thread here in the next day or two and making lineage official in the next week or two.
Click to expand...
Click to collapse
Great to hear it TDM.
Cannot give you enough kudos after lurking in the lineageOS test forum thread and seeing all the work you have been doing.
I may even give AOKP a try once you've had a chance to look at it. Lineage is great but it's been years since the Halcyon days of having _multiple_ viable on-stock Androids!