The galaxy s+ is, but dark_samus is using an Xperia device I believe because if the architecture
do you know which xperia device it is hes using as a base fr this device
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
The galaxy s+ is, but dark_samus is using an Xperia device I believe because if the architecture
do you know which xperia device it is hes using as a base fr this device
The farthest I ever got with cm was cm11 for the nexus 4...I built it just to see if I could build it before trying to port to the reverb
i see. was it successful
hmm i guess thats a sign. but ik you have other builds though. so is there any way for you to recompile the nexus build and move other builds to an external hard disk so you can continue?
i just thought of something, we may need to install a custom bootloader to get the cm9 or cm10 to work. i had the galaxy precedent and in order for me to get a gingerbread rom on it i had to install a gingerbread custom bootloader on it. it may be the same case for this device. who knows it might be the bootloader that might be preventing that from booting since its not custom. what do you all think on this. all answers accepted
true haha. but its the only option i can think of. from what i can tell everything for the cm10 rom built properly and everything was confirmed built but wasnt booting. so what if the bootloader is rejecting the rom. even if it does flash like others said its not guaranteed to boot. so what if the bootloader was rejecting it while booting?
OK bootloader is the LAST place to look, some people confuse boot and bootloader, boot is a partition on the device which DOES need to be modified to make CM boot, the boot partition contains a kernel and a ramdisk inside a special type of (iirc, not 100% sure if this is the type of archive file, don't quote me on it) .tar.gz archive, which contains 2 things the kernel and ramdisk,the bootloader unpacks the boot partition which is loaded into the RAM it in turn executes the kernel, which in turn loads the ramdisk which executes service to bring android up, so far it seems that proprietary files are seeming to be the problem with cm10 along with some ramdisk stuff if you'd like to learn more PM me your gmail and I'll pop you into Google hangouts
he was very clear. but my question is why the ramdisk isnt responding to the new rom? does the kernel aid in with the booting too?
hmm well how compatable is this phone with the galaxy ring? i heard samsung has a new kernel out for it and its kernel was compatable with this phone
hmm youve compiled a custom kernel for this device right
As far as I know, there are 2 custom kernels for this phone:hmm youve compiled a custom kernel for this device right