- Nov 17, 2011
- 190
- 3
- 0
Does anyone know if Cyanogen team is working on a Rom for this now we have root? Thanks
Sent from my LG-VM670 using Xparent Pink Tapatalk 2
Sent from my LG-VM670 using Xparent Pink Tapatalk 2
Does anyone know if Cyanogen team is working on a Rom for this now we have root? Thanks
Sent from my LG-VM670 using Xparent Pink Tapatalk 2
Last i heard the bout loader is still locked but I'm sure they will
Sent from my DROID RAZR using Android Central Forums
Well its been rooted so what's the boot loader have to do with anything
Sent from my LG-VM670 using Xparent Pink Tapatalk 2
Unlocking the boot loader gives you much more and allows you to flash things such as kernels or new radios to your phone. You need boot loader to do this, not simply root. CM has a ROM in dev for the GS3 last I heard and same as an unofficial AOKP port but with a locked boot loader (last I saw online someone from CM is coming close to cracking it) it won't be nearly as good.
I don't think this is 100% accurate. AFAIK the Droid X bootloader was never fully unlocked, and it still ran CM7. Bootloader does allow you to do more, but it isn't a guaranteed "NO" when it comes to Cyanogen. Again, as far as I know.
SGS3 on Verizon Update
So for anyone who is wondering, this last weekend I finalized a kexec-based boot sequence for CM9 on the d2vzw (Samsung Galaxy S3, Verizon variant) that will allow standard installs to the device.
All of the kexec internals are now stored on the system partition, and cold booting into the stock kernel will result in the following:
1.) boot is hijacked immediately after the filesystems are mounted
2.) kexec-boot.zip is copied to /cache and set to auto-flash on reboot
3.) device is rebooted into recovery
4.) kexec-boot.zip is auto-flashed without user interaction
5.) device is kexec-rebooted with androidboot.mode=kexec
6.) boot is not hijacked since it is within a kexec environment
7.) the system is now booted with a custom kernel
This means we now have custom kernels that can be booted directly from a cold boot (no booting into recovery and flashing a zip manually, that will be done for you). Also this means that all of the kexec internals are on the /system partition, so backups and restores from recovery function as expected. The only downside to this is that the boot process actually involved 2 quick reboots, but it's preferable IMO to having to flash manually from recovery.
The main problem still existing with the device is the lack of data connectivity. This is currently being looked into. Voice calls and SMS function as expected, but the SIM appears to be failing provisioning resulting in no 3G/4G connectivity.
I'll keep you posted.
I don't think this is 100% accurate. AFAIK the Droid X bootloader was never fully unlocked, and it still ran CM7. Bootloader does allow you to do more, but it isn't a guaranteed "NO" when it comes to Cyanogen. Again, as far as I know.