I dunno if this helps anyone. However my friend just got an 8gb active and he's running the 4.55.97 update. He then decided to root using the root tool and replaced the boot.img file and then used the root step. He has all the features of the latest version (ie percent on battery). And he is able to install zeam launcher and custom apps and whatnot.

Can he run

adb pull /system system

then zip the system folder that's created and send it to me?

I can build from that, hopefully.

Next rom update will use bda's latest kernel, pending stability.

Originally Posted by ClearD

Can he run

adb pull /system system

then zip the system folder that's created and send it to me?

I can build from that, hopefully.

Next rom update will use bda's latest kernel, pending stability.

I'll see what I can get from him and get back to you.

Finally got boot to flash from updater script !!!

---

Originally Posted by ClearD

Any idea of the syntax to flash the boot.img properly? I keep getting status 7 error (assert failed) with the binary from the official OTA update (the one that includes the boot.img).

I have to say... This was one hell of a b**ch !!! The reason boot flashing has been failing is because of the faulty recovery we have, hence the Beta status of our recovery.

For this to work, you will need busybox installed on your system folder.

Meaning... Make sure busybox libraries are present in /system/xbin.

If you are flashing a new ROM, run package_extract_dir first to dump system first.

Then place the following code at the very end of the updater script to flash boot.img :

ui_print("");
ui_print("Test - Boot - Flasher");
ui_print("Mounting System");
mount("ext3", "MMC", "/dev/block/mmcblk1p18", "/system");
ui_print("");
ui_print("Stage 1... Extracting");
package_extract_dir("bootimg", "/tmp");
ui_print("Stage 2... Setting Perms");
set_perm(0, 0, 0777, "/tmp/boot.img");
ui_print("Stage 3... Flashing Boot");
run_program("/system/xbin/busybox", "dd", "if=/tmp/boot.img", "of=/dev/block/mmcblk1p12", "bs=1024");
ui_print("Unmounting System");
unmount("/system");
ui_print("");
ui_print("Flash Successful");
ui_print("");

Note:

- No need to mount system again if you've done that in the beginning of the script.
- I've placed boot.img in a separate folder named bootimg within the zip file.
- Remember to set /tmp/boot.img permissions to give busybox access to boot.img

I have tested this and can confirm that it is working 100%.

Enjoy :)

The 4.55.97 files are up for real this time (no one really needs 4.55.78 at this point), sorry for the delay, thanks for all the help, and enjoy. =)

*crosses fingers*

(double post; remember to thank CEnnis91 and utkanos for their hard work!)

successful update .97

---

Successfully updated to ROOTED .97 now
Thanks CEnnis91
NA

5.6.0!

---

Sorry guys for another update; hopefully you can forgive me. 5.6.0 stock and rooted are now available (I said it would be easy once we got all the kinks out). There also might be some more good news: because I obtained a completely stock system.img (thanks embeem), it's possible that updating will again be possible via motocast if you flash the stock-5.6.0-update.zip. We won't know for sure until the next update however.

HOW?

---

Originally Posted by bdaman80

Test kernel seems fine, but I need some testers on same as me, and different versions than both of mine. I'm on 4.55.78


Sent from my DeathStar disabled device

How 'd you do it? Overclocking1000MHZ？

---------- Post added at 02:42 AM ---------- Previous post was at 02:24 AM ----------

Originally Posted by CEnnis91

Sorry guys for another update; hopefully you can forgive me. 5.6.0 stock and rooted are now available (I said it would be easy once we got all the kinks out). There also might be some more good news: because I obtained a completely stock system.img (thanks embeem), it's possible that updating will again be possible via motocast if you flash the stock-5.6.0-update.zip. We won't know for sure until the next update however.

Look forward to update for a long time, Alway staying at the4.55.78

I got this one.

OMAP3 Processor, same one used in the Droid 2; Droid 2 has it running at 1 Ghz, so why shouldn't we? They toned ours down for the watch, presumably to save battery power.