628 replies to this topic

[icefloe01]

My coworker is already being pestered with the update notice. Anything he can do?

[SamuriHL]

Same thing you did.

Sent from my Xoom using Tapatalk 4

[mikeymax]

If I'm unlocked and was rooted , took the update by accident literally at a DR. Appt. Is it safe or what specifically can I flash to go back ...get root... be safe with root keeper and then reupdate... or not update at all? Without any potential risk? I assume not much but I gotta ask..

Sent from my DROID RAZR HD using Tapatalk

[mikeymax]

Ignore

Sent from my DROID RAZR HD using Tapatalk

[SamuriHL]

If I'm unlocked and was rooted , took the update by accident literally at a DR. Appt. Is it safe or what specifically can I flash to go back ...get root... be safe with root keeper and then reupdate... or not update at all? Without any potential risk? I assume not much but I gotta ask..

Sent from my DROID RAZR HD using Tapatalk

 

If you're unlocked, just use my universal root script or just flash custom recovery (CWM or TWRP) and flash the SuperSU zip.  Downgrading should be possible if you really want but you'd have to use my House of Moto with the universal script as the TZ partition can NOT be downgraded even on unlocked phones.

[icefloe01]

My coworker is already being pestered with the update notice. Anything he can do?

 

 

Same thing you did.

Sent from my Xoom using Tapatalk 4

 

Apparently his phone had already downloaded it. Even after the rename and reboot, it's still pestering him to install. One thing, he did not do a hard reboot.  He just did a "Power Off", waited, then turned it back on. Does it need the hard reboot to effect the change or is it just because it downloaded it already? If it did, would deleting the update file work? Where is it located?

[SamuriHL]

Wipe the cache. That will clear it. Not a factory reset, just a cache wipe in recovery.

Sent from my Xoom using Tapatalk 4

[mikeymax]

I meant locked

Sent from my DROID RAZR HD using Tapatalk

[icefloe01]

Wipe the cache. That will clear it. Not a factory reset, just a cache wipe in recovery.

Sent from my Xoom using Tapatalk 4

 

Ouch. That was a heart stopping chore. He apparently has one of the XT926s that doesn't like wiping it's a--, er, cache. Took 5 attempts to do it. Hit reboot now and it did nothing. Two attempts at a hard boot and it finally came to life. His heart was pounding.

[SamuriHL]

I meant locked

Sent from my DROID RAZR HD using Tapatalk

 

Oh.  Um, yea, if you're locked and on the latest update, you're SOL for now until a new root exploit comes out.

[SamuriHL]

Ouch. That was a heart stopping chore. He apparently has one of the XT926s that doesn't like wiping it's a--, er, cache. Took 5 attempts to do it. Hit reboot now and it did nothing. Two attempts at a hard boot and it finally came to life. His heart was pounding.

 

Yikes!  That's not fun.

[icefloe01]

Somehow I just started receiving notification that 9.18.94 is ready for download. I just checked and the blur updater is still renamed. How did it check for the update? Instead of just adding "_bak" to the end of the filename before the .apk extension, should I have renamed the apk part to bak instead?

[shane1]

Yes I'm pretty sure it should be .apkbak

[icefloe01]

Done and done. The .odex file as well just to be safe. Off to reboot. Thank you!

[sharklasers]

Worked on my Droid razr maxx hd (9.18.79 xt926) At first it froze at the command line box on the pushing exploit step but i switched to a different usb port tried again and it worked great (I also used the cable that device came with)

[eygraber]

And I quote myself.  People on locked phones should not have been the ones to test this...

 

I'm on a locked 9.18.79 (xt926) and I used motochopper 1.3 to root. I'm getting the notification to update now. I don't want to because I'm not sure if root would survive (even with voodoo), but I did run the OTA zip through an app called OTA Verifier. It checks the read-only assertion part of the updater script, and I got this error from it:

    FAILED: line #824
    assert(apply_path_check("EMMC:boot:10485...dee9"));

    apply_patch_check: file (boot) does not exist or cannot be accessed

I read somewhere that motochopper 1.3 changes the boot file. Is this what is causing the problem? If so, once (if?) a root exploit is found for the new update, how would I resolve this issue?

[SamuriHL]

When you ran motochopper it never finished. The last step is to put the boot partition back. You'll have to flash that manually before you take the update should you decide to.

Sent from my Xoom using Tapatalk 4

[eygraber]

When you ran motochopper it never finished. The last step is to put the boot partition back. You'll have to flash that manually before you take the update should you decide to.

Sent from my Xoom using Tapatalk 4

And I should use the boot.img from the boot_new directory that comes with motochopper?

[SamuriHL]

Correct.

Sent from my Xoom using Tapatalk 4

[eygraber]

And I should use the boot.img from the boot_new directory that comes with motochopper?

 

 

Correct.

Sent from my Xoom using Tapatalk 4

 

I just tried this and I'm getting the same error.