Related
http://www.multiupload.com/7FCS3EORXF
The source for the lgp506 (Aka LG Thrive), im hoping devs well get on this, and apply a p506 version for there existing roms, for them to work with the p506 correctly. Otherwise, from what i've been able to surmise is, the only issue with porting roms from the p500 to other variations seem to correlate from the kernel.
and in regard to the p506, the current cm7 rom port works, only the screen is 8-bit and showing only 3-4 pallets of blue.
Hope this source helps out.
if you dont like or cant use multiupload, other means to get the source is just going to http://www.lg.com/global/support/opensource/opensource.jsp and searching lgp506go.
its 2.2 or 2.2.x ?
ccdreadcc said:
its 2.2 or 2.2.x ?
Click to expand...
Click to collapse
i thought it was 2.2.1
Interesting
Searching the internet for phone specs.
I diff'ed the source against the P500 source.
Practically the only difference is that the P506 has two framebuffer(?) drivers (novatek and hitachi) rather than one (just hitachi), with runtime detection of hw.
Relevant kernel config is CONFIG_FB_MSM_MDDI_NOVATEK_HVGA.
Since /proc/mtd is the same for P500 and P506, I guess roms and recoveries go through with just this display glitch issue, but it'd be great to have a proper one.
Does anyone know whether it is possible to just replace the zImage in CWM/amon_ra, or a compilation is required?
I have installed a 2.2.1 P500 ROM on my P506 with my stock kernel and I can verify that the color issue is history. We just need devs to port there kernels to the P506 and we can utilize the ROMs for the P500.
Please devs help us Thrive / P506 users out a little!
Sent from my LG-P506 using XDA Premium App
Ciaox u use linux?
Any devs looking into this?
Sent from my LG-P506 using XDA Premium App
devs wont be interested, if p506 user base is very low. getting more p506 users to comment here might get devs attention ><
ccdreadcc said:
Ciaox u use linux?
Click to expand...
Click to collapse
Yes I do. Why?
BTW I love AT&T
What do you guys need? A kernel? If so get more users to coment this topic and I'll see if its reasonable to release a kernel with the extra framebuffer. But I need to be sure the user base of this phone is high enough, otherwise it's pointless.
We mostly need help with understanding the following:
Will sticking the stock P506 zImage in a cwm/amon_ra recovery, keeping the initrd and everything, just work? e.g., using mkbootimg.sh ?
The diff between P500 and P506 froyo kernels has the following changes. Are they all relevant? were some of these fixed upstream?
Novatek fb driver (and renaming of hitachi fb functions)
ami304 driver changes (support for gyro and pedometer?), including ami306 support(?) EDIT: it's the driver from Optimus V.
some minor added functionality in drivers/input/sensor/kr3dh.c
LG's fix for the touchscreen bug (?) in drivers/input/touchscreen/mcs6000_ts.c
Camera modifications (parameters, added sports scene) in /drivers/media/video/msm/isx005*
MMC changes, incl. not powering down sdcard on suspend
A change of BRCM_WLAN_SLOT to 100 instead of 2 (BCM432X related)
Units change (mul by 10) in drivers/power/msm_battery.c
USB changes in drivers/usb/gadget/msm72k*
added a call to sock_setsockopt in net/socket.c, function kernel_connect()
Would applying the diff to your kernel (or any froyo kernel) would just compile and work (assuming no conflicts)?
Would applying the diff to a gingerbread kernel work, or gingerbread has some major changes?
Is the change (at least the FB one) simple enough to convince you and/or other P500 kernel developers to incorporate it in your builds (so no fork needed)?
Thanks,
R.
+1 for interest, I've already rooted but when I looked into roms etc. for the P506 I found there weren't any so I'd be glad to test recoveries/roms
OK, I got some answers for my questions, and some new questions.
Swapping p506 zImage for p500 zImage in AmonRa 2.2.1b recovery soft-bricks. Fastboot FTW.
Swapping p506 boot.img in a stock P500h rom boots and works in full color, but the logcat is filled with an AMI304-related error.
E/AmitDaemon( 1289): [AMI304D] AMI304MID_IOCTL_GET_CONTROL error​(I also get "battery hot" warnings, but maybe they're unrelated).
Not sure if accelerometer works, had to restore nandroid.
webosguru: do you have this error as well?
I think I saw that some IOCTL codes have changed in the new ami304 driver, so I guess it should be skipped in custom compilation (or fix AmitDaemon, wherever it is).
EDIT: I think this could be also fixed by using system/bin/ami304d from the AT&T rom. I wonder what other native executables I should take from stock AT&T?
I cannot find the 3 buttons required to get to recovery. Power+Home gets to fastboot, with or without VolDown. I have to use adb or rom manager.
Any ideas?
When booting a recovery via fastboot boot recovery.img, keys are not functioning. adb works, so I can flash and/or reboot recovery, but why won't they work?
I tried to grab froyo source via the repo tool, but it seems to download every piece of code ever written and then fail with some missing manifests. Ideas?
Next thing I'll do is probably to deodex and debloat the stock AT&T rom.
just happy progress, however small, is being made. Lots of smiles today.
Pursuing the deodexed stock AT&T rom path, I found out that my stock backup is (next to) worthless; it didn't include OOB info, and unyaffs fails to extract it.
I used dd if=/dev/mtdX of=/sdcard/mtdX.img instead of nandroid. I wonder if dd'ing it back and then a nandroid backup would work.
I have been following this thread. I am new to android but can help with testing out kernels.
Sent from my LG-P506 using XDA App
Really would love to see some ROM development happen for the Thrive!
Sent from my LG-P506 using XDA App
webosguru said:
I have installed a 2.2.1 P500 ROM on my P506 with my stock kernel and I can verify that the color issue is history. We just need devs to port there kernels to the P506 and we can utilize the ROMs for the P500.
Please devs help us Thrive / P506 users out a little!
Sent from my LG-P506 using XDA Premium App
Click to expand...
Click to collapse
How did you do the install without a custom recovery? Or, if you have a custom recovery, which one did you use?
And, +1 re wanting a custom kernel from P506/P505.
sd_matto said:
How did you do the install without a custom recovery? Or, if you have a custom recovery, which one did you use?
Click to expand...
Click to collapse
Install CWM for Optimus One P500 via Rom Manager.
Recovery shows weird colors, but regular rom uses a different kernel.
Now pick your favorite P500 FroYo rom, replace boot.img with your original boot.img and flash via CWM.
I still do not advise it since the ami304 daemon has problems, btw.
So I found a tool on XDA that allows me to put the ROM of choice to be ported and the base ROM. I'm trying to port Paranoid Android 2.00 since we don't have it, and now that we have somewhat steady CM10 nightlies I *should* be able to use it as a base. (The tool is called RomPorter)
So I went ahead and compiled a ROM, but I'm not sure if I should flash. I mean if it was this easy to port ROM's wouldn't we have ROM's just popping up everywhere? I used the HTC One X International version's PA 2.00 as the input ROM btw. I have some coding experience in Java but if it's this easy to port without any coding required why hasn't it been done yet? Just curious. I looked at the CM9 guide to porting PA and I have to make a linux portal and all those things. Basically my main question is, will this work? I don't want to flash and end up hard bricking my phone. I went and checked the build.prop, and framework and it all seemed like a hybrid of CM10 nightly and Paranoid Android 2.00 but is there something I'm missing?
Thanks a lot guys! I'm tired of just being somebody who stands on the side and waits for things to get ported or created. I'm taking a heavy load in college but I want to try and port something at least to contribute.
Using the international base could cause a brick unless you ported an evita kernel too. The international one x has a different partition layout as well.
Read read read, check, double check and triple check. When your confident its possibly bootable, sure that it is not harmful THEN flash it to your device first. Ports are always going to start with bugs. Don't expect perfection, expect a WIP. Importantly, have fun learning. Most importantly , FIRST FLASH IS ALWAYS YOURS :beer::beer:
Added People port roms all the time for themselves. Now posting one on xda and maintaining a thread with dozens-hundreds of followers is a WHOLE DIFFERENT STORY
I just want to try it but I'm afraid it'll brick. I mean what's the worst case scenario? Boot loop then restore to my nandroid? Or being stuck with a brick forever? I don't have a backup phone at the moment lol. Maybe I should invest in one.
If you flash something that overwrites hboot you're hard bricked. That's what I meant by different partition layout.
Here's a easier start for jb paranoid Android port.....dload the HTC evo 4g lte jb paranoid port rom, unzip it, delete the included boot.img, use a hox boot.img from a hox jb rom to replace it with. Zip it and flash it.(use the one XL cm10 boot.img) It will give u a bootable port of jb paranoid Android. Then like most ports, you will start fixing bugs. Camera and wifi won't work, you will need to fix those for sure. But a lot will work so start with priority bug fix#1 and keep on goin
Added: paranoid android rom I would consider the land of the brave for first time porting. U may encounter fixes to be harder than some less modified roms.
I understand now what the scare was. But when taking the Evo LTE ROM and pushing our own boot.img it'll allow me to at least get it started to see what I need to get going and fix! That's a fantastic idea. I'm going to head over there now and see what ROM's they have. I mean technically we share very similar devices internally right? I haven't looked into the Evo specs much.
Shaddy-Z. said:
I understand now what the scare was. But when taking the Evo LTE ROM and pushing our own boot.img it'll allow me to at least get it started to see what I need to get going and fix! That's a fantastic idea. I'm going to head over there now and see what ROM's they have. I mean technically we share very similar devices internally right? I haven't looked into the Evo specs much.
Click to expand...
Click to collapse
make sure you pull out any radio images you find in the roms you look at.
Could I push the ones from a cm10 nightly?
No idea. Probably. Or just don't include one.
getting in contact with the developer for the Evo PA ROM. Hopefully this goes somewhere.
Don't we already have a pa rom? You've inspired me though. I'm going to look at porting roms too.
The PA ROM is still ICS, and the biggest killer is that the multi-touch fix is not incorporated because the ROM was cooked pre kernel release unfortunately. The latest update the dev was supposed to release didn't boot and I don't know what happened after that.
And do it! The more devs the better. I want some variety in this little community.
By the way, PARANOIDANDROID 2.00 is not out yet. The last OFFICIAL release is 1.992: Changelog. As for the port, I would love to port roms to our device, since it is my primary device.
I already port ROMs from the i9100 to i777(SGSII Internation to AT&T US Version), but this is a VERY simple operation. And you can use a pre-made program to port by ktoonsez called Flashaholics, but it is only for porting to the i777. I hope we eventually get that far but these 2 devices are far more similar that the One X/OneXL or Evo LTE/One XL.
Just use the latest paranoid rom with the latest cm10 boot.img. I did it a few times when I had my hox. And gunny is right. Either pull the radio or flash a hox radio after u flash ur port and u will get signal with working talk, text. 3g should work too, mms won't, streaming video will be iffy. Just run thru the major stuff, write down what's broken, prioritize it, then always make a nandroid of your previous build so u can revert back if fixes make things worse
---------- Post added at 01:09 AM ---------- Previous post was at 01:03 AM ----------
He's gonna work off a unofficial paranoidandroid jb 4.1 from the evo lte. It'll boot but there will be plenty of fixing to do. I think its for his use/learning, not sure if he plans on putting it up on forums
I don't plan on uploading it to the forums unless I get the features working. I'm off all day tomorrow so I'll probably give it a shot to see what I can do.
I also realized PA is not 2.00 after I posted that, buts its still a JB Paranoid ROM so it'll do for now while I learn.
It's really good seeing someone (who isn't a regular dev that I know of?) taking such initiative and asking the right questions and such in order to get some dev'ing underway.
Great job! :good:
stnguyen09 said:
It's really good seeing someone (who isn't a regular dev that I know of?) taking such initiative and asking the right questions and such in order to get some dev'ing underway.
Great job! :good:
Click to expand...
Click to collapse
Thanks! I appreciate it So I got a little ahead of myself and tried it tonight, I'm slowly following a guide and I THOUGHT I was doing everything correctly but it won't flash after "Verifying system partition size" and I got an error. This seems to be a common problem that leads to the updater script, so I'm going to take a look at it when I get up. Could just be a syntax error, or maybe I'm just building it wrong I'm kinda tired
U can always nab the updater script from cm10 hox also. Its been a while and I forgot to mention that. I had the same issue with the evo rooms and that did the trick:beer:
I tried: using the ports updater, the base, and a collaboration of the two and it still didn't go through. Maybe its something else ? I'll try it again to double check.
This something i had stumbled on accident trying to dual boot my LG G2x (p999) using the LG Optimus 2x (P990) Dual Boot tutorial.
If done correctly, your your LG G2x will be model P990 instead of P999. you will be using Optimus 2x Roms instead of G2x Roms. Everything Should you need will be on this besides the 2 roms you want to dual boot http://forum.xda-developers.com/showthread.php?t=1856090
Well... Thanks for sharing but...
The Baseband and RIL still working with the G2X??
I doubt so. I have the dual boot for the G2X it works well but even if you use the p990 files the baseban and ril would have to be for the g2x, and i doubt thing will work out. It is better to port the roms instead.
I am looking for a straightforward explanation of the file systems for the P990 and the P999 especially a comparison and, better, a utility/script that would enable selecting the one to be used to format memory. I am also looking for information about how to port between the P990 to and from the P999. Do you have it or know where any of that information is located?
Rafase282 said:
I doubt so. I have the dual boot for the G2X it works well but even if you use the p990 files the baseban and ril would have to be for the g2x, and i doubt thing will work out. It is better to port the roms instead.
Click to expand...
Click to collapse
In theory, If you were using the current March 2012 baseband (v21y), couldn't you just flash OWAIN's NewBaseband.zip, and then run GetRIL to make sure the RIL is updated to the baseband?
That should get you a working phone (in p990 mode).
New2my8125 said:
In theory, If you were using the current March 2012 baseband (v21y), couldn't you just flash OWAIN's NewBaseband.zip, and then run GetRIL to make sure the RIL is updated to the baseband?
That should get you a working phone (in p990 mode).
Click to expand...
Click to collapse
Maybe I was not clear on my post. The devices are most similar. The differences are on the radio (baseband, irl, etc), partition scheme, and the p990 has fm radio while the p999 does not. They are made for different carries so while you may be able to use those files, what they are intended to do is to change the partition scheme to allow two roms to fit, and then use some scripts to switch roms using the boot.imgs you provide and changing system, data, and other files like that to a different name so each rom has independent files, they are all store on data.
So the problem is that your radio stays the same, so by flashing the wrong baseband/radio you will just brick your phone. It can be recovered on these particular devices using nvflash but overall it should not work as just changing every entry from p999 to p990. That can be done when building the rom, just change the assertion script or turn it off and you can flash anything on the partitions given that they are the right size, it will still not work tho.
This will be really usefull when a Full stable ICS O2X rom come out...
DankoFGL said:
This will be really usefull when a Full stable ICS O2X rom come out...
Click to expand...
Click to collapse
No, when such thing comes out it will be ported, no need to change the partition scheme or anything.
Rafase282 said:
No, when such thing comes out it will be ported, no need to change the partition scheme or anything.
Click to expand...
Click to collapse
Not necessarily true! No O2X OFFICIAL Rom has ever been ported successfully to the G2X. CM7/CM9/MIUI yes, because we have source. Factory/Official ROMs? Never 100% successfully.
I had a GB O2X Rom running on my G2X once before, but I forget what I had to do to make it happen. DId nothing with KDZ's, I modded the kernel somehow. But, as others discovered, it wasn't possible to get the radio working. Curious if Owain's fix would work as a port as suggested previously in this thread.
Would be nice to have a native O2X Rom to run... I think 9/10ths of the "crazy bat**** stupid" problems the G2X has are due to the fact that LG basically stripped out LG Framework to make it appear AOSP without actually being AOSP. The problem is, they didn't strip out all of the LG Framework, only the parts that you see. So the G2X has a lot of unused and half-connected code on stock Roms.
And, as others said, it could be very useful for ICS...
But as I've said... Several of us have had O2X roms ported. The hitch has always been lack of cellular radio.
Rafase282 said:
I doubt so. I have the dual boot for the G2X it works well but even if you use the p990 files the baseban and ril would have to be for the g2x, and i doubt thing will work out. It is better to port the roms instead.
Click to expand...
Click to collapse
Is there a thread for G2X dual boot? This is the first I've heard of it, I'd hate to have to try to rewrite the O2X scripts myself, but dual boot sounds very nice.
Core Memory said:
I am looking for a straightforward explanation of the file systems for the P990 and the P999 especially a comparison and, better, a utility/script that would enable selecting the one to be used to format memory. I am also looking for information about how to port between the P990 to and from the P999. Do you have it or know where any of that information is located?
Click to expand...
Click to collapse
I hate to say it but probably the best explanation would be the compile scripts for source. From the limited research I've done(kanging the CM10 blind builds), once you build the P990/SU990 source with the P999 script, you pretty much "fill in the blanks/diff" by using a full P999 rom aka CM10 kang (somewhere I remember seeing a list of what the source doesn't include). I know someone ran df or fdisk or something of that nature on a SU990 and posted the results with the ICS rom so the differences are sorta documented....Or you could ask wkpark.I might myself as I speak and write his native language!
bakedpatato said:
I hate to say it but probably the best explanation would be the compile scripts for source. From the limited research I've done(kanging the CM10 blind builds), once you build the P990/SU990 source with the P999 script, you pretty much "fill in the blanks/diff" by using a full P999 rom aka CM10 kang (somewhere I remember seeing a list of what the source doesn't include). I know someone ran df or fdisk or something of that nature on a SU990 and posted the results with the ICS rom so the differences are sorta documented....Or you could ask wkpark.I might myself as I speak and write his native language!
Click to expand...
Click to collapse
Please ask.
Yes, you can easily dual boot ROMs with the G2X, I do it with Temaesk and my stock ROM. Very convenient. Search through the thread and there should be someone who posted the proper partitions for our phone for use with NVFlash.
If you don't know what you're doing, or are new to this stuff and don't know what the word "troubleshooting" means, then stay away from it as most of the help is for the O2X and I've semi-bricked/bootlooped my phone before I got the complete feel for dual booting it correctly and how to update kernels for it and such.
buru898 said:
Yes, you can easily dual boot ROMs with the G2X, I do it with Temaesk and my stock ROM. Very convenient. Search through the thread and there should be someone who posted the proper partitions for our phone for use with NVFlash.
If you don't know what you're doing, or are new to this stuff and don't know what the word "troubleshooting" means, then stay away from it as most of the help is for the O2X and I've semi-bricked/bootlooped my phone before I got the complete feel for dual booting it correctly and how to update kernels for it and such.
Click to expand...
Click to collapse
Isn't the partition setup in the .cfg file used with NVFlash?
I just want to simply know if it's it possible to flash any O2x rom on the G2x? I don't care if the radio isn't working, I already use my Galaxy Nexus for calling/texting etc. I just want to get a touch of ICS/Other O2x roms.
breadland said:
I just want to simply know if it's it possible to flash any O2x rom on the G2x? I don't care if the radio isn't working, I already use my Galaxy Nexus for calling/texting etc. I just want to get a touch of ICS/Other O2x roms.
Click to expand...
Click to collapse
Answering your question the answer is not. If you don't care about the radio then use the dualboot method or just properly change the partition scheme and flash your rom and let us know what happens. Since it doesnt seem to be your main phone you wont miss anything if it bricks. As far as I know our phone is "unbrickable".
Core Memory said:
Please ask.
Click to expand...
Click to collapse
I posted on daum(my name roughly translates to 'angry at butt') but I think wkpark thinks i'm some sort of script kiddie or something due to the name...hah.
I had no luck installing an O2x rom on my G2x. The nvflash part worked, but the installation part was too confusing for me so I probably did something wrong. I'm wondering if anyone actually managed to install an O2x rom on the G2x successfully.
breadland said:
I had no luck installing an O2x rom on my G2x. The nvflash part worked, but the installation part was too confusing for me so I probably did something wrong. I'm wondering if anyone actually managed to install an O2x rom on the G2x successfully.
Click to expand...
Click to collapse
No, not directly.
Help
Hello I hope someone reads this.
I have accidentally partitioned my P999 with the P990 all in one tool. It only takes now p990 roms, but no baseband. It is working quite nicely, but is has no mobile service. How can I repartition my internal sd to be p999 again?
Peter
Szippy said:
Hello I hope someone reads this.
I have accidentally partitioned my P999 with the P990 all in one tool. It only takes now p990 roms, but no baseband. It is working quite nicely, but is has no mobile service. How can I repartition my internal sd to be p999 again?
Peter
Click to expand...
Click to collapse
Use either ROM for recovery or cleanup batch. Search development threads.
-- The noob says:
Bow your head for the android's prayer... I am an android, but I can change, if I have to, I guess
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.
Would a ROM built for a J700F/H/M be compatible with a J700T? They have the same CPU and GPU. The only difference I notice is the supported network technologies, but I may of overlooked other differences.
If not completely compatible without modification, what would need to be changed?
I'm guessing I could just flash and see what happens, but I don't have time right now to deal with a bricked phone if it does go wrong.
Thanks.
vekenti said:
Would a ROM built for a J700F/H/M be compatible with a J700T? They have the same CPU and GPU. The only difference I notice is the supported network technologies, but I may of overlooked other differences.
If not completely compatible without modification, what would need to be changed?
I'm guessing I could just flash and see what happens, but I don't have time right now to deal with a bricked phone if it does go wrong.
Thanks.
Click to expand...
Click to collapse
Only some ROM's can be flashed and all features don't transfer. The wifi setup is different and so is the camera. The kernel codes are different as well so kernel specific ROM'S won't flash either.
Would it be easy to fix the wifi and such? I don't have much experience with ROM porting, and I was hoping that this device would be the one that I can finally get some experience, because you would think it would be pretty easy to convert J700F/H/M ROMS to J700T ROMS.
vekenti said:
Would it be easy to fix the wifi and such? I don't have much experience with ROM porting, and I was hoping that this device would be the one that I can finally get some experience, because you would think it would be pretty easy to convert J700F/H/M ROMS to J700T ROMS.
Click to expand...
Click to collapse
I would imagine it would be pretty easy to port over some of the ROM's, I'm currently running Alloosh's N7 V3, but without digging through the kernel codes for each ROM it's hard to say. You would have to set up your build environment and identify the differences and change them, trust me it's a long sometimes pain staking process ha. It's not as hard as building a different OS from source or porting over other software, but it will still take some time.
I've gotten the camera to finally work and wifi and Hotspot are running fine too, but there's still issues I'm looking into. Just start doing some research and see what you're comfortable with diving into.
You need to try using your device stock kernel with those roms
messi2050 said:
You need to try using your device stock kernel with those roms
Click to expand...
Click to collapse
Do you know where I can find the stock kernel file for the J700T? Ive had no luck finding it myself.
vekenti said:
Do you know where I can find the stock kernel file for the J700T? Ive had no luck finding it myself.
Click to expand...
Click to collapse
You can make a backup of your current kernel using apps like flashify...etc
Thanks
I got the pixel experience rom to boot on my j700t with messi2050's v1 kernel. Rebooted every 2-10 minutes. It looked great i wish i could use it for my daily runner. I just reflashed pk6. Which rom to try this with next.
Dustinsk22 said:
I got the pixel experience rom to boot on my j700t with messi2050's v1 kernel. Rebooted every 2-10 minutes. It looked great i wish i could use it for my daily runner. I just reflashed pk6. Which rom to try this with next.
Click to expand...
Click to collapse
I'm using Messi's kernel on the Note 7 ROM by Allosh.
I use his kernel on almost every flash I do, dudes awesome for porting it for the T.
Too bad he removed all his downloads though. In the process of making my own SE permissive kernel for the J700t.
Just busy with life currently.