What's new
DroidForums.net | Android Forum & News

This is a sample guest message. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!

Droid 2 global d2g GINGERBREAD DEFINITELY COMING!

2nd init lets us reinitialize a custom init process with custom binary and rc script.
Translation lol: it starts the init instance a second time, the first one frozen, and the second doing the job. 2nd init changes how a new init is called and injects code to restart the 1st init-but into a different program. If really simply put, another hijack, which circumvents the locked bootloader issue. (You can customise the whole system partition)
It needs to be combined with something called sh hijack, a hijack to run a custom program for a script that calls /system/bin/sh; the script itself occurs in an early stage, which is init as well. This from what I understood from linux manual and a brief look at what 2nd init is.

Sent from somewhere in a strangereal world...

Yep...Thank Byak, I finally found CVPS' blog post about it.

It a method of making a shadow not of the Kernel just the boot folder Init uses to boot into system which is read only. So it's really just making a new startup routine to get a clean no PID system that CM needs to work.

Quite ingenious really! LOL

Would be so much easier if that damn Bootloader were just unlocked! LOL
 
this throws a solid wrench into any locking that Motorola does. I wonder what their devs would say if someone told them about 2nd init and the bootloader bypass....ahhahahaha....

You know and quite a few people (and an equal amount otherwise) felt it was only a matter of time before the bootloader would get hacked! It may not have been hacked by definition, but I think this counts lol
 
Yup, it's like kicking them where it hurts. :icon_ owned:
I think this should be kept reasonably quiet though from moto......who knows what devious things they could come up with to block this.

Sent from my Droid using DroidForums
D1-can't stop going back to it lol
 
Yup, it's like kicking them where it hurts. :icon_ owned:
I think this should be kept reasonably quiet though from moto......who knows what devious things they could come up with to block this.

Sent from my Droid using DroidForums
D1-can't stop going back to it lol

Keep it quiet? Afaik, four moto devices are getting ports of CM now, D2G included (I would know, I'm almost ready to put out a solid alpha) :D

Sent from my White DROID 2 GLOBAL.
 
And I am infinitely happy to hear that! Ive been running my phone stock since last week, waiting for I dont know why the GB update. And I dont know why because I will put CM on the phone regardless of what Moto's update 'fixes'. With 2nd init and the near limitless though frustrating possibilities it brings I don't ever have a reason to stay stock (and all the haters talking about how good the OG droid is for being unlocked can finally shove a foot in it!!!)

Angel and bikedude, you are my heroes.
 
This 2nd init approach can easily be blocked by splitting off a new partition for /boot, relocating init scripts there, and setting the read-only hardware flag for that part of NAND space. But it's a hassle.

I doubt Motorola cares much because not a lot of people will do this anyway.
 
With this, I can only surmise that we can probably port other roms to devices with locked bootloaders:happy:

My guess is the porting issues (while they could be solved by unlocking) are more to do with drivers than bootloaders. What 2nd Init does really is wipe out any vestiges of stock running before it loads the custom code.
from what I read, 2nd Init doesn't really bypass or usurp the locked bootloader it just hijacks and kills any proccess started by it so that we start off with a clean 1 PID system to boot into. Before 2nd Init we pretty much ran our customcode along with proccesses that we didn't need. Now those proccesses are gone and we start off clean meaning better performance and less compatability issues cause there is nothing running that can conflict.
But Bikerdude probably has a better handle on that than I do!

Keep it quiet? Afaik, four moto devices are getting ports of CM now, D2G included (I would know, I'm almost ready to put out a solid alpha) :D

Sent from my White DROID 2 GLOBAL.

Can't wait to try it BD...I am not one to run Beta because I need the damn thing to work but your CM7 port is going to be the exception to that rule! LOL

As for those who think Moto can try and stop 2nd Init in the future you can forget about it! We already have the froyo SBFs to undo anything they try to do to stop it from working. In fact if I'm not mistaken their OTA GB does precisely that which is why you have to SBF back to froyo to put CM7 in.

For me once CM7 is up and running on my phone I won't care what the hell Moto does because I won't ever take another OTA from them after CM is installed.
 
I guess my only question regarding CM is that, is there anything in a Gingerbread kernel that is worthwhile to have? What are the benefits to having GB run on a GB kernel, versus a GB cyanogen running on a froyo kernel?
 
I guess my only question regarding CM is that, is there anything in a Gingerbread kernel that is worthwhile to have? What are the benefits to having GB run on a GB kernel, versus a GB cyanogen running on a froyo kernel?

Don't comfuse the kernel with the OS...
All the kernels are really Linux and are similar in a sense (but not exactly)to a BIOS in a PC.

So it is doubtful that the Kernal has anything you need in it on a GB version compared to a Froyo.

The kernel is all about running Linux not any particular flavor of it.

What might be different is they protected the Init process better which is why we need to start from Froyo and not GB Kernel. But as for operation and compatability there should be nothing in GB we need that isn't already in the Froyo Kernel. I doubt the kernel has much to do with actual phone features.
 
We could probably get a sim card fix and a few other things like gsm radio firmware/drivers/etc out of an ota, but it's true, it isn't of much use after we extract what we need. Heck, I'm not even interested in running the friggin' OTA. Going to just get OTA, do a system dump+copy over the update file, and sbf back to froyo. Blur=That bad. Give it a boot to the head :laugh:
 
We could probably get a sim card fix and a few other things like gsm radio firmware/drivers/etc out of an ota, but it's true, it isn't of much use after we extract what we need. Heck, I'm not even interested in running the friggin' OTA. Going to just get OTA, do a system dump+copy over the update file, and sbf back to froyo. Blur=That bad. Give it a boot to the head :laugh:

the new blur is actually fantastic, ive used it for a while and i love it over stock, but yeah i dont think im gonna run stock, at least until it gets rooted and i can get rid of all the bloatware.

i already know im going to be jumping a lot between CM and stock rooted like i do now with stock and hexen :icon_evil:
 
We could probably get a sim card fix and a few other things like gsm radio firmware/drivers/etc out of an ota, but it's true, it isn't of much use after we extract what we need. Heck, I'm not even interested in running the friggin' OTA. Going to just get OTA, do a system dump+copy over the update file, and sbf back to froyo. Blur=That bad. Give it a boot to the head :laugh:

the new blur is actually fantastic, ive used it for a while and i love it over stock, but yeah i dont think im gonna run stock, at least until it gets rooted and i can get rid of all the bloatware.

i already know im going to be jumping a lot between CM and stock rooted like i do now with stock and hexen :icon_evil:
And I'm betting that practice will stop once you have run CM for a while! LOL
 
Back
Top