What would be the chances of it unlocking the bootloader itself?
Ok, no problem, sorry.hoodlum47 said:As of now this project is on an indefinite hold (read my last post for the reason) and sadly sbf'ing did not help, I contacted Kenneth again about this problem and he has yet to get back to me so until he does nothing can be done at this moment. Also I would appreciate it if you can take down that thread with the update I posted in it because: 1.The only noticeable change is a different kernel. 2. It's a step backwards from .602 performance wise and 3. I may get in trouble with Moto if it spreads because of the first two reasons. Please take it into consideration anrichardson.
I deleted the links other then the one that links to this thread and reported the thread to be deleted. Hope you keep getting results though.hoodlum47 said:There's no need to be sorry, I mean I understand why you did it, hell I'd probably do the same if this thing wasn't being done by me =P
You are probably right, cause it seemed very buggy.hoodlum47 said:I'm unsure about that because this seems to be different than what I pulled from the servers. What I pulled was 8MB this is 113MB so its either a complete build to make it more stable or the same build with a reworked system to patch the latest root exploit.
The one thing I didnt do was a factory reset after installing. But it shouldn't matter either. Nobody is going to want to factory reset after doing an update."hoodlum47 said:I just found the reason for that, the post is mixed up. VZW's site says the update goes up to 113MB depending on what version your on, plus the images posted still shows it as 8MB in size. Looks like Moto is taking a step backwards stability-wise, it patches a bug I've never even heard of.