244 replies to this topic

[spainter]

Unfortunately I got this phone after the previous user had already accepted the update.  Maybe it's possible to do something with SafeStrap?

Nope The .15 build on a locked device hasn't been touched.  The phone is over 2 years old and I know of no one working on exploiting the .15 WP.

[manoj]

any root available for this update 

183.46.15

 

[SamuriHL]

If only that's been asked and answered in this thread "a couple tines now"....

[SamuriHL]

I've updated the op for some clarity on the root thing. I'm sure no one will bother reading it just like the last couple posts of this thread have been ignored.

[soocold]

Ya that's pretty clear

Sent from my Nexus 6 using Tapatalk

[aaqibanees]

any bootloader unlock available for this version 183.46.15? except motopocalypse

[johnthehillbilly]

any bootloader unlock available for this version 183.46.15? except motopocalypse

No

[aaqibanees]

No

My phone is rooted

[johnthehillbilly]

My phone is rooted

If you are on this version.... And rooted.... Then you must be unlocked already .....

[SamuriHL]

If you are on this version.... And rooted.... Then you must be unlocked already .....

 

Not necessarily.  If they upgraded to this version WHILE rooted, it'd keep root. As soon as they FXZ for any reason, root-be-gone™.

[johnthehillbilly]

Pleasure.. but motopocalypse is not working..

As far as we know, it will not work again ever....

[aaqibanees]

As far as we know, it will not work again ever....

[samterra]

 

Are there any FKZ for KDA20.62-15?

 

Most of below does need to be stated for folks on this forum but saying just in case it helps someone help me -

 

Per Recovery Menu, I have KDA20.62-15 but all I can find anywhere is FKZ KDA20.62-15.1 which gives me: Failed flashing process. 2/20 flash partition "gpt.bin" -> Phone returned FAIL - which from what I understand is because version mismatch. Only other things I found were 62-10x which fail with "preflash validation failed for GPT" because it's a downgrade.

 

I have no interest in rooting the device. It is locked. I was just using my phone when services started restarting (1 day before my contract expired) so I did soft-reset and landed in the Motorola Red Circle of death - all I can do is get to recovery screen or Fastboot screen.

 

I've already wiped-data/factory-reset (per Verizon advice) before I started looking online and found this forum - so I have no data on the phone to be salvaged. Just want to get this thing to work. Motorola rep said to send it in (for $150). If it was hardware failure that was one thing but having to get new device/contract or pay $150 for a software error just rankles.

 

Thanks all!

[SamuriHL]

No idea at all what you're saying here.  It's FXZ, for one.   And the FXZ posted in this thread is the latest for the XT926.  GPT failure can be caused by a whole bunch of reasons.  Just saying it failed without telling any more information is meaningless.  Could be caused by using the wrong USB cable, wrong USB port, old drivers, wrong version of RSD, low power state on the phone, etc, etc.  It's not possible to know why it failed in your case without more information other than stating it failed.

[samterra]

No idea at all what you're saying here.  It's FXZ, for one.   And the FXZ posted in this thread is the latest for the XT926.  GPT failure can be caused by a whole bunch of reasons.  Just saying it failed without telling any more information is meaningless.  Could be caused by using the wrong USB cable, wrong USB port, old drivers, wrong version of RSD, low power state on the phone, etc, etc.  It's not possible to know why it failed in your case without more information other than stating it failed.

Sorry yes FXZ - realized after I read back my own post. 

 

What more information to provide? Battery shows ok in Fastboot, USB Cable is original motorola supplied data cable that came with the phone. (Don't know what it means to have 'wrong USB port' - aren't they all same - this is Win7/hp laptop).

I was using RSDLite 6.1.5 but switched to 6.2.4 and retried. Had installed latest motorola drivers; tried installing the same from link you provided and it confirmed same version (reinstall with the mediafire msi gave repair/remove 6.4.0 install options and selecting repair 90% of the way through says "account exists" and ends - other than the 'account exists' part it seems to suggest everything is fine). 

 

Below is SWDL snippet for latest run. Also attaching full SWDL. Thanks a lot for your help!

 

02/01/15 11:00:15  --------------------------------------------------------------------------------

02/01/15 11:00:17  New Log Started For Software Download.

02/01/15 11:01:14  Arrival, interface=28(0x0), device id=1636460.

02/01/15 11:01:56  The FlashLog key is turned off.

02/01/15 11:02:03  Multi upgrade started for 1 phones

02/01/15 11:02:03  [Device ID: 0] 1/20 oem fb_mode_set

02/01/15 11:02:03  [Device ID: 0] 2/20 flash partition "gpt.bin"

02/01/15 11:02:04  ERROR: 2/20 flash partition "gpt.bin" -> Phone returned FAIL. - on device ID 0.

02/01/15 11:02:04  [Device ID: 0] 2/20 flash partition "gpt.bin" -> Phone returned FAIL.

02/01/15 11:02:04  ERROR: Failed flashing process. - on device ID 0.

02/01/15 11:02:04  Multi upgrade finished.

Attached Files

•  SWDL.txt   26.96KB   2 downloads

[SamuriHL]

USB ports are not all the same.  USB 2.0 vs USB 3 makes a huge difference.

[samterra]

Thanks! Looked up specs for the laptop. All USB ports on my Win7 laptop are 2.0.

 

3.0 is required for this? My MacPro has 3.0. Is there an RSDLite for Mac? Thanks again!

[johnthehillbilly]

Thanks! Looked up specs for the laptop. All USB ports on my Win7 laptop are 2.0.

3.0 is required for this? My MacPro has 3.0. Is there an RSDLite for Mac? Thanks again!

3.0 USB is BAD for this... 2.0 is what you want

[SamuriHL]

I have a hunch.  Just for fun, post the AP Fastboot screen text from your phone.  ALL of it.  I want to see something.

[samterra]

AP Fastboot Flash Mode (S)

10.9B(*) (sha-61146a2, 2014-07-29 03:17:13)

eMMC Info: 16GB

 

Device is Locked, Status Code: 0

 

Battery OK

 

Transfer Mode:

USB Connected

 

Fastboot Reason: Boot menu selected

usb connected

 

---

Above is the current state after last attempt with 6.2.4 version.

There were other messages last night but those disappear as it seemed like device didn't charge so I went to recovery mode/red circle screen for charging.