Related
This was the tweet fromCvpcs!!! (We haz a booting "true" AOSP system with 0 blur! http://www.youtube.com/watch?v=PPqfIRZP7Mc Still very buggy but I'm working on it)
Sent from my DROIDX using XDA App
booyah! let get er done!
Sound like good news!
Still, could anybody explain what AOSP boot means? Will this enable us to boot a custom kernel on the x?
I have no idea what this means except 100% no blur sounds awesome!
AOSP essentially means it was built completely from source. Not built based on Moto's own build with their custom framework (blur) crap. It is a true complete Vanilla rom.
Android Open Source Project
http://source.android.com/
So they got an AOSP rom to run using the stock moto kernal? Because obv we can't change kernals at this point yet
Sent from my DROIDX using XDA App
If they got an aosp to run they should be able to modify the kernel no? Thought that was the while point of the exploit nenolod is working on.
Sent from my DROIDX using Tapatalk
this is too awesome.
Joe92T said:
So they got an AOSP rom to run using the stock moto kernal? Because obv we can't change kernals at this point yet
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
No, from my limited understanding, this isn't using the Stock Kernel. They've figured out a way to get NVRAM into Engineering Mode..
Someone correct me if I'm wrong.
vonfeldt7 said:
No, from my limited understanding, this isn't using the Stock Kernel. They've figured out a way to get NVRAM into Engineering Mode..
Someone correct me if I'm wrong.
Click to expand...
Click to collapse
This AOSP has actually been running for a while now. Its being developed by cvpcs, the same guy who's been developing the Sapphire roms for Droid. I don't know if he's using the recent exploit that has made the rumor-mill lately. He claims its a true AOSP boot, which implies a custom kernel compiled from source. However, for all we know he could still be using the Moto 2.2 kernel, but replaced everything else in user space with fresh, compiled code.
Either way, its interesting. Despite Motorola's best attempts, it looks like the Droid X (and Droid 2 by implication) will soon be free of its eFuse prison, allowing us users the choice of what to run on this device.
We won't be getting rid of eFuse, as it's hard coded into the silicon itself in NVRAM, as I understand it. Its just that folks are working on getting the keys to the prison .
hi guys,
i am sniffle, a member of the CCRoms Team that produces Sapphire(Droid 1), Ruby(HTC Incredible), Obsidian(Droid X), Emerald(HTC Evo)
to clarify a few things.
this does NOT utilize the bootloader hack, it is a custom boot setup that initializes the boot process a second time to load the custom rom after the bootloader has ran all of its checks. It technically could be considered a second boot setup as it does initialize the boot process a second time.
it does NOT use a custom kernel, it uses the stock kernel, since the bootloader is not locked. the process to actually be able to use this rom is quite involved. When we are ready to release, there will be detailed instructions for flashing. If you aren't comfortable with ADB, terminal executions this rom will not be for you.
i will try to explain more as the questions come up, but for the most part that's all there is to say... other than to say that more is broken at this point than fixed. as more news comes available i will let you guys know.
sniffle said:
hi guys,
i am sniffle, a member of the CCRoms Team that produces Sapphire(Droid 1), Ruby(HTC Incredible), Obsidian(Droid X), Emerald(HTC Evo)
to clarify a few things.
this does NOT utilize the bootloader hack, it is a custom boot setup that initializes the boot process a second time to load the custom rom after the bootloader has ran all of its checks. It technically could be considered a second boot setup as it does initialize the boot process a second time.
it does NOT use a custom kernel, it uses the stock kernel, since the bootloader is not locked. the process to actually be able to use this rom is quite involved. When we are ready to release, there will be detailed instructions for flashing. If you aren't comfortable with ADB, terminal executions this rom will not be for you.
i will try to explain more as the questions come up, but for the most part that's all there is to say... other than to say that more is broken at this point than fixed. as more news comes available i will let you guys know.
Click to expand...
Click to collapse
Thank you guys for your hard work, I am sure that most of the community is as excited as I am to see your work make it to the X. I love the boot ani from the video, and even though this is my first android phone the things Ive read about your teams previous releases has me EXCITED for this to hit.
appreciate your update and clarification, sniffle!
OMG, aosp 2.2 for my droidx would be awesome. Nice to set someone working on it, props and kudoes.
Sent from my PC36100 using XDA App
i hear this is almost 100% working!
LT1UltraZ said:
i hear this is almost 100% working!
Click to expand...
Click to collapse
Heard the same this morning. Very excited!
dogswind said:
Heard the same this morning. Very excited!
Click to expand...
Click to collapse
Would love a source on this info.
Almost 100% is a bit too strong of a descriptor, there are still some major bugs like rebooting on sleep(hitting the power button to turn the screen off) and a few others on top of that. With our next sapphire and Ruby release we will be making the latest build publicly available for other development to help figure out a fix for these problems.
Hi Devs,
Can anyone answer the question, Is it possible to dual boot i9000 with different custom Roms?
it is possible and is under development, but has not been completed yet, as im sure you can understand how difficult it must be.
I don't think I would be game enough to try that..
Good question
Sent from my GT-I9000 using XDA Premium App
Very Possible (i think)
Galaxy S is a kind of mini compact compute,
using the bootloader, using two kernels side by side on the phone.
as logical question , this my logical answer.
i think by this year, smart developers will reach that point instead of focusing on thems ,app and wallpapers.
this is intresting
thanks
bekh said:
Very Possible (i think)
Galaxy S is a kind of mini compact compute,
using the bootloader, using two kernels side by side on the phone.
as logical question , this my logical answer.
i think by this year, smart developers will reach that point instead of focusing on thems ,app and wallpapers.
this is intresting
thanks
Click to expand...
Click to collapse
That bootloader thing isn't as easy as you might think
And you have to figure out how to partition the phone because two roms mean two /system and, as far as I know, the space is lean as it is now.
It should be possible but I don't want to be the guy who does it (although I would respect that man (or woman) a great deal)
Well multi boots require separate partitions plus a multi boot loader. Quite an ask for a phone. in theory possible, but sounds pretty difficult to me.
Sent from my GTI9000 using XDA App, gingerbread 2.2.3 jvk rooted, ADW launcher + gingerbread theme
whilst its not really dual boot you could use CWM to make backups and restore the different roms if you want to regularly switch? not what you are asking I know but a work around perhaps.
i would be happy for an app that runs a system of the sd card, kinda like how they used to run android on the HD2. Click the app and it would boot android restart and it boots back to winmo coz thats whats on the NAND .
This would good for people that want to test a ROM, mod it, theme it without flashing the orgional ROM. A Virtual machine if you will
jebise101 said:
i would be happy for an app that runs a system of the sd card, kinda like how they used to run android on the HD2. Click the app and it would boot android restart and it boots back to winmo coz thats whats on the NAND .
This would good for people that want to test a ROM, mod it, theme it without flashing the orgional ROM. A Virtual machine if you will
Click to expand...
Click to collapse
hey guy i have think about what you said if dev can develope multi loader like computer that can we have both winphone 7 with android or maemo with bada or meego with ios! that sounds good and i think we can do that cause we have three diffrent storage in galaxy s. that have 2 gig rom that we have used it for android by now and we make it lagfix and change it from rfs to ext. another storage is internal nand that is 8 or 16 gig that we can use for further os like ios. and at last for blue tooth or else we can use external sd storage up to 32 gig i think galaxy s is more up than n900 or hd2 so we can nand and port real os on it!
BootManager - ROM multiboot
Hello, someone knows if this app works on galaxy s i9000?, I have a version of this device sold exclusively here in Brazil it is called I9000B, the only difference for the I9000, is that my tv is digital!
I wud love to hav dual boot - Android n WP7 (like HTC HD2), but having 2 android OS doesnt make any sense!
Actually does so, this way we can enjoy two different roms at the same time, can have the best of two worlds!
No updates? I thought we could just have an entry in the recovery mod which backs up the old kernel, flashes a new kernel, maybe modded to mount the /system and /data filesystems from sdcard images (system.img & data.img), replaces init.rc to avoid problematic mounts, and then boots the other rom. then, to reboot in the original rom, enter recovery and select the default one. I just want to know what are the problems we could find with this method. I can help, if someone is interested in doing this. I'm not a dev, but I can prepare images, edit init.rc, and if you give me the source I may be able to edit the recovery. I really want dual boot on my i9000, to test roms without wipes and backups, to have choice, to have a recovery rom in case something goes wrong with the default one and I'm not at home. For instance, it happened to me, that sometimes I couldn't listen to music when I was on the bus, due to roms' problems. I wish I could boot an emergency rom in cases like that.
casseres2001 said:
BootManager - ROM multiboot
Hello, someone knows if this app works on galaxy s i9000?, I have a version of this device sold exclusively here in Brazil it is called I9000B, the only difference for the I9000, is that my tv is digital!
Click to expand...
Click to collapse
no it will not work, becoause of bootpartiton
but i really cant understand , why skilled kerneldeveloper cant develope any dualboot kernel: Main rom at Phone-Rom and second rom just at sd-card
...
...that would be nice to have a dual boot on my samsung !!!!
Hey!
After looking through the G2X Forums, i see there is a hell of lot of roms out there. (Heck they even startet porting ICS!!) That's much more than the 3-4 we have. Is it possible to port a G2X rom to our O2X? Isn't it just a change of partitions?
'Off course we dont get radio, but how many of us actually use it
Oh, and BTW, i am not a developer... More of a dummy
+1
Sent from my LG-P990 using XDA App
sorry, i dont thing there's much chance of it happening.
& dont worry about ice cream sandwich, we will probably get it soon enough after google releases the source code
so what is real difference between both of them? i mean from the outside they look the same...i have a optimus 2x and i really would like to know
schölli said:
so what is real difference between both of them? i mean from the outside they look the same...i have a optimus 2x and i really would like to know
Click to expand...
Click to collapse
The phones are almost identical, though each of them have very different filesystems which is near impossible to change. plus i think it can run hspda 850mhz frequency i think. Other than that, they are exactly the same.
schölli said:
so what is real difference between both of them? i mean from the outside they look the same...i have a optimus 2x and i really would like to know
Click to expand...
Click to collapse
Different partition layout and different radio hardware.
It doesn't really have anymore ROMs then we do, just some minor changes, but they're based on 2-3 different roms like ours (Ok, they do have ICS port also). There just are more cooks, not that many devs. BUT, they do have a few more kernels and I don't see a reason why we couldn't use their CM-kernels on our phone if we wanted. But maybe we dont? Their stock probably won't work on LG stock, so.
Edit: I changed my mind, there isn't even more kernels. We don't need them.
But is there not a way to make ROM's able to work on each others devices?
Im thinking:
You flash a ROM for the G2X on our O2X.
Then you flash some G2X to O2X ROM Converter changing the partitions and HSPDA freq?
Badabim badabum.. lockscreen!
Possible or? If possible, then we have the 2x dev power
Balano said:
But is there not a way to make ROM's able to work on each others devices?
Im thinking:
You flash a ROM for the G2X on our O2X.
Then you flash some G2X to O2X ROM Converter changing the partitions and HSPDA freq?
Badabim badabum.. lockscreen!
Possible or? If possible, then we have the 2x dev power
Click to expand...
Click to collapse
This can be done. Although I don't know to which extent. You will need to have hardware checks on which drivers to load, config, partition schemes, etc. It's a actually a very neat idea. Good for experimentation
More like linux running on different hardware configurations I'd love to see the day when we have a generic Android base that works on all devices. Then for specialized drivers, you can get them from the vendors -- bliss!
That would actually be nice - But would the shared Rom then not be huge? 1gb+?
Maybe some developers would look in to it and maybe share a beta for us to test out on different Roms and types of 2X'es. .
Balano said:
That would actually be nice - But would the shared Rom then not be huge? 1gb+?
Maybe some developers would look in to it and maybe share a beta for us to test out on different Roms and types of 2X'es. .
Click to expand...
Click to collapse
Yep. It could be significantly bigger than today's roms since you will bundle generic drivers for all supported devices. But that's easy to fix. The bigger hurdle is to make it work.
Sent from my Optimus 2X using xda premium
Balano said:
Hey!
After looking through the G2X Forums, i see there is a hell of lot of roms out there. (Heck they even startet porting ICS!!) That's much more than the 3-4 we have. Is it possible to port a G2X rom to our O2X? Isn't it just a change of partitions?
'Off course we dont get radio, but how many of us actually use it
Oh, and BTW, i am not a developer... More of a dummy
Click to expand...
Click to collapse
+1
because there will be lot more of rom choices then
Sorry but what's code for g2x i mean alike p990
Sent from my LG-P990 using Tapatalk
spica1234 said:
Sorry but what's code for g2x i mean alike p990
Sent from my LG-P990 using Tapatalk
Click to expand...
Click to collapse
P999 i think.
Sent from my LG-P990 using Tapatalk
Yeah it's the P999 for the G2X and WIND Mobile O2X.
Ok thank you
Sent from my LG-P990 using Tapatalk
I have made a 2.3.4 rom for the G2X (based on an unreleased LG-L95G device) and planning on porting your new Italian rom to the G2X. If the flash is CWM compatible you don't have to worry about partitions as you only flash the system image and maybe a compatible kernel. The updater script just tells CWM to mount the system parition (the kernel knows which one) and you copy the files to the system. The kernel (at least for the G2X) is just a file called boot.img and you tell CWM to flash the boot image in a similar manner. I think it is just a matter of replacing the RIL files with the correct ones so the rom can talk to the radio, and swapping out drivers for other differences in the hardware. Other than the radio, as far as i can tell, the phones have virtually identical hardware. I think it would be a good project for someone and not that hard to port one of our G2X roms to your O2X devices.
jboxer said:
I have made a 2.3.4 rom for the G2X (based on an unreleased LG-L95G device) and planning on porting your new Italian rom to the G2X. If the flash is CWM compatible you don't have to worry about partitions as you only flash the system image and maybe a compatible kernel. The updater script just tells CWM to mount the system parition (the kernel knows which one) and you copy the files to the system. The kernel (at least for the G2X) is just a file called boot.img and you tell CWM to flash the boot image in a similar manner. I think it is just a matter of replacing the RIL files with the correct ones so the rom can talk to the radio, and swapping out drivers for other differences in the hardware. Other than the radio, as far as i can tell, the phones have virtually identical hardware. I think it would be a good project for someone and not that hard to port one of our G2X roms to your O2X devices.
Click to expand...
Click to collapse
Sounds good actually.
After you port the italian ROM to the G2X, tell us the difficulty and if you encountered any issues.
So, you are saying that a swap in radiodrivers and a modification to the updater script is all that is too it?
Balano said:
Sounds good actually.
After you port the italian ROM to the G2X, tell us the difficulty and if you encountered any issues.
So, you are saying that a swap in radiodrivers and a modification to the updater script is all that is too it?
Click to expand...
Click to collapse
That plus other stuff. The thing that is concerning me is that in the installer script for the P990 rom there is a volume called "dbdata" being mounted. We don't have a mount called this on the P999, so I need to know what this is used for. Maybe we have something similar but has a different name. I need someone who is knowledgeable about the P990 roms to tell me what this volume is used for. But the thing that makes no sense is that the installer script is simply mounting it, doing nothing with it and then accounting it, so maybe it's a non-issue. The rom itself looks surprisingly similar to the one for the L95G with the exception of the UI customizations. I really think the only difference between the two devices is the radio chip because TMO wanted faster 3G (21Mbps vs 7.2Mbps). I don't know why memory is partitioned differently but that should not be an issue for putting the rom together, as the kernel takes care of all that. We have to hope that everything works using the kernel from the L95G. Due to partitioning differences using the P990 kernel is not an option.
There is nothing on the O2X that corresponds to "dbdata" and it certainly can't be mounted in recovery as there is no entry for it in recovery.fstab
Hi everyone!
I'm looking to become a future dev of the Samsung Captivate Glide, but as we're awaiting the official ICS from AT&T the forum right now is pretty dead. We have a project going but nobody to guide us, and we wish to compile CM9 or AOSP ICS. Would anyone take me in and teach me the basics of ROMing? I would greatly appreciate it! I have a Mac and Windows, I'm not sure if Linux is required :|
~Aquethys
the rom is the least of the worries to get dev going on your phone, getting the kernel going is the hard part. does your phone have the source code released?
I don't believe so, people in our ics port thread are saying we don't have a working ics kernel. We do have a gingerbread kernel though... :/
How would I start?
Sent from my SAMSUNG-SGH-I927R using xda premium
well you take parts from the GB kernel and apply it to parts from the AOSP kernel, and troubleshoot until it boots. then you troubleshoot all the other issues, there will be issues, then you can start doing fancy things like add cwm. then tweak the kernel....
start reading on kernels, ramdisk, rils, libs, and drivers, linux, compiling, AOSP, github repositories.
you might be ready to take on this task in 6 months.... minimum
dont take that as snooty, ive been on here over a year, and know jack squat about half the things i just told you to study. though i have no desire to build kernels myself. there is lots of great info scattered all over xda. but you will need an experienced dev, to port ICS. you need to know basic kernel modification stuff before trying to do something as big as porting a new android version from out your but.
automated compiling isnt as automated as it sounds.
Alright. What programs will I need to begin with? Hopefully an experienced dev can guide me, I'm not too good @ following guides/tutorials but I'll try my best!
Sent from my SAMSUNG-SGH-I927R using xda premium
EDIT: Made a dropbox account, hopefully you could guide me through the basics?
So, is this the source code for SGH-I927 you were talking about? I downloaded it, what do I do with it? Is it different for ICS and GB?
I am about to acquire a droid 4
I'm looking for the most up to date rooting method and safe strap installation.. I am by no means a "noob" lol.. I've been reading up on this device and I am currently under the impression that the ICS utility tool is the best method.. My primary device is the nexus but this will b a nice alternative for when I need my battery last longer than 5 hours lol
Secondly ... What is everyone's consensus on the ROM stability.. I am looking for the ROM that can be used as a daily driver.. Would love to hear AOKP is in that boat!!
I believe I've gone through all the stickies so if I missed anything feel free to bring it to my attention!!
Lastly I've owned other moto devices where I would b able to flash the stock image via rsd. Curious if this exists on this device..
To anyone who wants to help me out with some answers I thank u in advance
Sent from my Galaxy Nexus using xda premium
Kevin3328 said:
I am about to acquire a droid 4
I'm looking for the most up to date rooting method and safe strap installation.. I am by no means a "noob" lol.. I've been reading up on this device and I am currently under the impression that the ICS utility tool is the best method.. My primary device is the nexus but this will b a nice alternative for when I need my battery last longer than 5 hours lol
Secondly ... What is everyone's consensus on the ROM stability.. I am looking for the ROM that can be used as a daily driver.. Would love to hear AOKP is in that boat!!
I believe I've gone through all the stickies so if I missed anything feel free to bring it to my attention!!
Lastly I've owned other moto devices where I would b able to flash the stock image via rsd. Curious if this exists on this device..
To anyone who wants to help me out with some answers I thank u in advance
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Rooting/Flashing Stock: The easiest way to root your device is with the Droid 4 Utility ICS Only found here: http://forum.xda-developers.com/showthread.php?t=1779810. jsnweitzel did a bang up job making it simple to use. You can also use the utility to fastboot your phone back to stock.
Safestrap: The newest version of hashcode's safestrap can be found in this thread: http://forum.xda-developers.com/showthread.php?t=1688610. This will allow flashing to your stock partition as well as to multiple ROM slots.
ROMs: If you're looking for stability you're best bet is Eclipse ROM by myfishbear. It's ICS based but that is the reason it is pretty bug free. There are also various JB ROMS floating around that can be used as daily drivers depending on your appetite for bugs. CM10.1, KILLRom, and LiquidSmooth are all 4.2.1 based and all have the same bugs including blutooth not fully functional and the big one, incoming calls result in a black screen of death unless you have your ringtone set to silent. There are also an AOKP and CM10 builds based on 4.1.2. They still have the blutooth bug but incoming calls work fine. You can find threads for each of these ROMs in the Dev section except for KILLRom. I created a thread for that ROM in the General section.
Hope this helps!
Thanks for taking the time to answer it is much appreciates
Sent from my Galaxy Nexus using xda premium