[ICS Leak/CRC] Droid 4 Build 6.16.215

[G3T_UR_0WN_W1F1]

so where can i find the .215 kernal at???

 

[Danis]

so where can i find the .215 kernal at???

http://www.droidforums.net/forum/showthread.php?p=2192231

Sent from my XT894 running ICS

 

[siggma]

I'm on ICS leak 215. My flash player isn't working, it freezes the browser (browser, chrome, opera, and dolphin HD).

I'm thinking about reinstalling 215, is that possible without messing anything up?

If that doesn't work, does anyone know a workaround? Is anyone else having problems?

Thanks.

You can simply re-run the installation from SD without any issues. Boot into bootloader (both volume keys plus power) and select "recover" then re-run the 215 update. No need to reload GB 219 files. It will install on top of itself.

 

[siggma]

so where can i find the .215 kernal at???

Read the first post in this thread, the link is there!

I added a link to the 215 kernel image at the top of the page, sorry it wasn't there before.

 

[siggma]

I'm a little confused, in the README file it states that you need to download the kernel image (boot.img) for the leak version that you're going TO, and references SGMD1's post. But his page only has the leaked OTA zips, and I can't find a boot.img inside it, just boot.img.p. I'm probably just a moron this morning, but is that the same file, or is it a patch that brings the GB219 kernel up to date? If it's a different file, where is the boot.img for 215?

Sorry, forgot the link to the boot image for 215. It's been updated to include both original link and a mirror.

Thanks for noting that issue.

 

[siggma]

"This tool requires you to enter and run a single command using CMD.
The final command is: fastboot flash boot boot-6-16-215.img (assuming you are installing ICS 215 leak)
After it finished and you observe the word "writing" either manually reboot or enter: fastboot reboot via CMD."

where can i find this thing called cmd? what IS it??? im a little bit of a noob bt @ the same time no, cuz ive already flashed my fone before... also, where can i find the CMD thing? is it already included?

My thinking is if you don't know what CMD is you probably shouldn't be flashing your phone with any updates or roms. These ROMS and leaked updates are not for the computer illiterate. If you make one mistake you probably won't be able to recover.

That said, CMD is the windows command prompt. Hit START and type CMD and a black window will open. The command listed will only work if you successfully change to the directory where you unzipped the tool. It's way beyond the scope of this post to explain how to use a command prompt. I suggest you not update your phone in any other way than that recommended by Motorola and Verizon. Otherwise you're just asking for a brick...

The tools posted here and on XDA are quick and dirty scripts that do not have any built-in error correction or even error detection so if something goes wrong you have absolutely no way to recover unless you know what the script is doing and can manually undo or correct it. That is why there are three pages of warnings before you can proceed with the tool.

Good luck.

 

[siggma]

Awesome how-to on this. I've flashed a lot of other devices, but I'm an Android noob, so mega-thanks.

The one thing I'd suggest adding is on the last step, once you pick 'Recovery', you'll be presented with a red dead Android screen. Hit both volume keys to bring up the menu with the option to recover from sdcard. Having not flashed Android much, I was rather alarmed to get a red dead Android when I was expecting to see an option to install from SDcard. Cue heart-skipping moment until I realized what was up.

Yea, different updates look different. Some version updates present the red broken icon requiring you to hit both volume keys to get to the menu, others don't and I don't know what the difference is. But if you've done it before you'll figure it out. I'll add that, thanks.

 

[kenji91]

My thinking is if you don't know what CMD is you probably shouldn't be flashing your phone with any updates or roms. These ROMS and leaked updates are not for the computer illiterate. If you make one mistake you probably won't be able to recover.

I didn't want to say anything but I agree. Odds are, if you don't know what CMD is, you probably shouldn't be doing anything not official to your phone.

It's a form of hacking/programming. It may not be too complex for a hacker/programmer/experienced computer user, but it still is modifying the system files that make your phone functional.

 

[siggma]

E:signature verification failed when trying to apply the 215.zip update. Thoughts?

You didn't write all the files correctly or you didn't write the boot image correctly or your 215 file is corrupt. Double check you copied the correct files to the tool directory and flashed the correct boot image. The tool has been tested to work correctly. When you answer yes the last time it says "caution to the wind...what the hell..." and starts flashing files. You should see the files being written to the phone in 256K chunks. It copies a chunk then writes it then copies more then writes it. It should take about 20-30 minutes to complete all the files. If you don't see "writing" as it's flashing either your phone is in the wrong mode (ap flash mode right?) or you have the wrong files.


Or you didn't extract the blur...zip from the leak archive.

 

[siggma]

I'm having a mushy-brain day. Normally I can get this without help, today...dunno. Expired caffeine or something...

So, I downloaded D4.6.16.215.zip and put it on my SD Card. Looking inside it (now) I see Blur_Version.6.13.219.XT894.Verizon.en.US.zip. Did I need to pull out the Blur.zip, or leave everything in the D4.zip?

Remove the blur... and copy it to your phone. I'll update the instructions.

 

[siggma]

you opened the zip of the zip

That would probably do it... Duh... I added that to the instructions.

 

[xipher]

Had what I would say is my first "major" annoying bug since flashing on the 15th without a reboot since then, suddenly found myself stuck in 3G today, all day, even after enabling airplane mode and disabling it, a complete refusal to go back to 4G ALL DAY.

Power cycled the phone, suddenly, 4G without issues in the exact same spot that was only capable of 3G before.

 

[breaker1]

Stuck at waiting for device

I'm trying to update my ICS build to 215 but am stuck at waiting for device within the batch file.

I've got the Motorola drivers installed and my phone is in camera mode with usb debugging enabled.

I've tried rebooting the phone and my computer and neither of those things fixed it.

Any help would be very much appreciated.

 

[breaker1]

I'm trying to update my ICS build to 215 but am stuck at waiting for device within the batch file.

I've got the Motorola drivers installed and my phone is in camera mode with usb debugging enabled.

I've tried rebooting the phone and my computer and neither of those things fixed it.

Any help would be very much appreciated.

Did NOT read the directions, was trying to flash when then phone was booted. Went into AP Fastboot mode and it's working (hope it goes well)

 

[breaker1]

Quick update:
All's not well;
When flashing back the old files I got an error

sending 'devtree' (512 KB)... OKAY [ 0.053s]
writing 'devtree'... INFOPreflash validation failure
FAILED (remote: )

I've tried manually flashing the device tree file and get the same error each time.

When I reboot the device it just dumps me back into fastboot mode.

Any ideas? Could I just throw the old (new?) files back on from the image I originally used to install ICS?

----

I managed to reflash my phone to the point where I can get into recovery, but the install fails and gives me this message in the verification phase:

assert failed: apply_patch_check("MTD:boot:8388608:fe086e1f547082c3cf2a5f65dacb81fd232ecd89:8388608:ffa3f348207e25a0087cfb9684deca2e2cdc7d00")
E:Error in /tmp/sideload/package.zip
(Status 7)
Installation aborted.


After a poor sleep I got up at 6 and really sat down and looked at everything. Turned out to be (I assume) a bad copy of the update zip. I took the sd card out of my phone and hashed the downloaded file and the file on my card. The hashes were different, so I copied the file over just directly to my sd card. It's currently updating.