170 replies to this topic

[mdpatterson]

logic would suggest that I did update to the 18th or higher if it was out at that point in time the only thing that I know for sure is that I bought the phone on the 25th and maybe a few days afterwards I took the update that was offered and that was the only update I ever took so it could be an update to the 16th to the 18th or the 20 but I doubt its the 20 if thats only come out recently and I doubt its the 16 if the 16 update is old

[mdpatterson]

but as soon as I get back home I will verify to see what version updated to using the method posted earlier in about 10 minutes

[RikRong]

I think it's for sure now that it was updated as well as the new bootloader date

Yeah, I'd have to say it's a sure thing.  

[livinginkaos]

I think it's for sure now that it was updated as well as the new bootloader date

Agreed.

From My S4 Dev Edition

[cmh714]

I wish I'd recognized that on page one

[pdgillmore]

I wish I'd recognized that on page one

thats where i spotted it cause it is the same number that my razr m has but i unlocked before the update.

[mdpatterson]

on the prompt for the motopocalypse unlock it reads.....

[cmh714]

thats where i spotted it cause it is the same number that my razr m has but i unlocked before the update.

Yea my problem is I dont have an HD or the M so didnt recognize the numbering. Always good to have others look at things.

[mdpatterson]

device found

unlocking phone

pushing unlock tool

2396 kb/s

unlocking phone

trustzone target address resolved to 2a020a02

trustzone write failed: -11

cleaning up

unlocking complete. rebooting into bootloader mode

press enter once the phone has rebooted into bootloader mode

press any key to continue

[mdpatterson]

that's from the unlock that cmh714 just gave me

[cmh714]

EPIC FAIL.....

[mdpatterson]

fastboot says device LOCKED

[Memnoch73]

 

trustzone write failed: -11

 

 

THIS.

[SamuriHL]

Then you're done.  Can't be unlocked.  And will never be able to be unlocked.  The end I'm afraid.

[cmh714]

we tried, but you are hosed.....no unlocky for you

[pdgillmore]

Yea my problem is I dont have an HD or the M so didnt recognize the numbering. Always good to have others look at things.

absolutly correct. i would not have known if i didn't have the m

[mdpatterson]

well not really a fail. it was always going to fail, what you did was really a success, because now we know. as opposed to not knowing. Im assuming based on everything that's been written, the trustzone issue means the update was installed, sounds like that's the issue you've seen with other people

[cmh714]

absolutly correct. i would not have known if i didn't have the m

Thanks but where were you 2 or 3 hours ago j/k thx for pointing out what shouldve been obvious.

[cmh714]

well not really a fail. it was always going to fail, what you did was really a success, because now we know. as opposed to not knowing. Im assuming based on everything that's been written, the trustzone issue means the update was installed, sounds like that's the issue you've seen with other people

correct the update patched the hole that was used for unlocking.

[mdpatterson]

im assuming the new droid maxx hasn't been out long enough to be rooted yet. and since Motorola came out with the fix that blocks this unlock, the maxx will probably not be unlockable either?