446 replies to this topic

[Majormer]

Exciting!

[bnb]

Does it show 211 or 214 in the about status menu in the device?mine still shows that i'm on 211 after doing the update.

[jimgfitzgerald]

You guys are nucking futs.

[mattlgroff]

You come through again man. Just one quick question : I have the. 79 leak on my non-safe side & Hashcode's flashable .211 on my safe side so can I use the utility to flash the boot.img? Sent from my DROID RAZR using Tapatalk 2

The kernel is shared between both of your systems, Safestrap doesn't touch it.

You go to AP Fastboot from any of them and flash it with the option for 214 in the utility I posted.

[etrorteepe]

Does it show 211 or 214 in the about status menu in the device?mine still shows that i'm on 211 after doing the update.

Mine shows 214.

[Brad92]

Of course this has to drop while I'm out of town without a computer lol.

Basically, there's no other change except the kernel?

[altjx]

For those who have updated... how's the battery life? Mine sucks on. 211 and I'm definitely looking to hear back on results.

Sent from my DROID RAZR MAXX using Tapatalk 2.

[Nnnnr12]

So if i'm on Arctic rom .211 with safestrap what do I do? I'm kinda lost

[Brad92]

So if i'm on Arctic rom .211 with safestrap what do I do? I'm kinda lost

Use the tool in the second link and a computer. Open the tool and have your phone in AP Fast boot mode and flash the .214 boot.img

Reboot and enjoy

[Ahowe125]

Mine shows 214.

Did you use his utility or actually update with the zip file in motorecovery?

I used the utility and it still says .211, but I'm willing to bet the kernel version is different.

[beaton3344]

It's that time again folks... leaked updates! (Yay~!)

This time I got a special treat. I did not want to leave my comfortable place with safestrap installed and booted on Arctic Rom on 211 to fastboot the 6.12.181 files, re-upgrade to 211 stock, upgrade to 214 just to see a small difference in the kernel. Therefore. I pulled and patched the biggest part of this leak update which is the boot.img (New ICS 4.0.4 kernel, hopefully fixing issues with battery life people have on 211 now!).

So two things today:

• Update zip to install in MotoRecovery from stock 6.16.211
  

  Please Login or Register to see this Hidden Content

  
  MD5: 715AD085D246105EB9101F872CE4B604
  File Size: 6.7 MB
• Utility to flash the new kernel, and the ability to flash 211 kernel back + root if you want to.
  

  Please Login or Register to see this Hidden Content

  
  MD5: CBA714069ABCAFF145610D8EDD33D81B
  File Size: 15.5 MB

To root using the little utility, choose the option to flash the 6.14.85 boot.img, boot normally (have USB Debugging Enabled from Settings>Developer Options and the USB Mode set to MTP or Camera with latest moto drivers installeddrivers installed).

Then choose the root option in the utility, then go back to AP Fastboot and choose the option for 214 or 211, your choice. I suggest 214 since its newer

This will NOT get you stuck on an ICS leak and can be downgraded to 211 if you choose (or even 6.14.84 if you really wanted too.).

Use Moto Recovery - This will unroot you so have to use .85 to get root then flash back to .214... Working fine so far... Will report about battery later...

[thaijunk]

Use the tool in the second link and a computer. Open the tool and have your phone in AP Fast boot mode and flash the .214 boot.img

Reboot and enjoy

Hi Brad. I'm also on Arctic and running on the safe side right now. From the sound of it, it looks like it doesn't matter if you're on the safe side or non-safe side on when flashing the new kernel. Is this correct?
Thanks

[Brad92]

Hi Brad. I'm also on Arctic and running on the safe side right now. From the sound of it, it looks like it doesn't matter if you're on the safe side or non-safe side on when flashing the new kernel. Is this correct?
Thanks

Correct. Matt confirmed this earlier in the thread.

[etrorteepe]

Did you use his utility or actually update with the zip file in motorecovery?

I used the utility and it still says .211, but I'm willing to bet the kernel version is different.

The updater script updates build.prop, so just flashing the new kernel in fast boot is not going to make build.prop show a new system version.

Attached Files

•  Screenshot_2012-07-04-22-55-45.png   68.35KB   111 downloads

[mattlgroff]

Does it show 211 or 214 in the about status menu in the device?mine still shows that i'm on 211 after doing the update.

This doesn't change your System Version that would be an edit to your build.prop. if you flashed the img through utility.

Did you update through Recovery or just boot.img?

[Ahowe125]

The updater script updates build.prop, so just flashing the new kernel in fast boot is not going to make build.prop show a new system version.

Yup, found out after talking in the chat room that the newest kernel build date is Fri Jun 29 and the older .211 kernel was from like the 14th or something like that. Either way, if you use Matts utility through AP fastboot, dont be alarmed if your system version is still .211 in the info.

[Alex.Abraham]

Matt youve done it again!!!!! So excited to try this out next chance i get

[topdog031382]

So I might be missing something but correct me if I am wrong. I just used the utility to flash the .214 kernel then used the utility again to flash back to the original .211 kernel. My question is couldn't we use this same type of method to flash custom kernels in the future? Even though we have locked bootloaders how are we able to flash this updated kernel? Again it is late and I might not be thinking straight. Is that a stupid question?

[digdug1]

so, if we use the utility only will we still have root?

[etrorteepe]

So I might be missing something but correct me if I am wrong. I just used the utility to flash the .214 kernel then used the utility again to flash back to the original .211 kernel. My question is couldn't we use this same type of method to flash custom kernels in the future? Even though we have locked bootloaders how are we able to flash this updated kernel? Again it is late and I might not be thinking straight. Is that a stupid question?

Only signed kernels from the same secure version that the bootloader is on can be flashed.