7 replies to this topic

[t3knokon]

Hello HouseOfMoto peeps,

 

I'm running into dead ends with my device, but I'm hoping you might have some further insight.  I originally posted at XDA about my issue(s) and was directed to try a few things which haven't worked thus far.  Quick history on the device... It's a replacement for a physically damaged one, that was preloaded with 19.6.3 su2-3.3, and I applied sunshine and root.  After installing root verifying root status, then I enabled survival mode.  I took the OTA update (mistake?), which I assume was version 4.4.4 su6-7 , and after the install was complete the phone rebooted in to fastboot and has been stuck there ever since.  From fastboot, I've attempted to manually flash gpt, recovery, boot, and system images, but every attempt returns "failed to erase partition xxx, flash failed xxx."  To me it seems the partition access is denied.  Secondly, I attempted to use the BLBroke / Qualcomm method to put the phone into Qualcomm loader mode, and that won't happen either... again, "failed to erase partition sbl12, failed to flash sbl12."  Thirdly, I attempted your very own HoM flash tool, but after completing the setup and beginning flash, it fails saying flash failed and it moves on to the next image.

 

Your thoughts?

 

 

-t3k

[spainter]

You will probably have to flash the 4.4.4 su6-7 full file or newer to it. Here are some google sites for that fxz file.  Make sure you choose the one for your exact model since 1080 has a couple vairiants ie maxx mini ultra.

https://www.google.c...=utf-8&oe=utf-8

[t3knokon]

CFC-obakem_verizon-user-4.4.4-SU6-7-release-keys.xml

this is what I was attempting to use.  As soon as RSD gets to the images to flash it fails, saying flashing failed.  On the phone it says "Failed to erase partition" and then the system halts.

[spainter]

CFC-obakem_verizon-user-4.4.4-SU6-7-release-keys.xml

this is what I was attempting to use.  As soon as RSD gets to the images to flash it fails, saying flashing failed.  On the phone it says "Failed to erase partition" and then the system halts.

Try this one.

1FF-obake-maxx_verizon-user-4.4.4-SU6-7.2-release-keys.xml.zip 1.0.0

http://motofirmware....ase-keysxmlzip/

[t3knokon]

I tried this one just now via RSD:   1FF-obake-maxx_verizon-user-4.4.4-SU6-7.2-release-keys.xml.zip 1.0.0 and it fails.

Also, I tried to flash images individually but I get back "flash failed, failed to erase partition"

[spainter]

Ok lets go back to the basics.  Make sure you are using a usb 2.0 port and the cable is a moto cable, not from a 3rd party charger etc.  Try changing ports on the computer just make sure you are usb 2.0 and not  through a hub. Motorola usb drivers are up to date and not been altered. The latest version of RSDLite is 6.24.  You may also want to look at House Of Moto 4.1 and see if that is something you want to try.

[t3knokon]

Ok lets go back to the basics.  Make sure you are using a usb 2.0 port and the cable is a moto cable, not from a 3rd party charger etc.  Try changing ports on the computer just make sure you are usb 2.0 and not  through a hub. Motorola usb drivers are up to date and not been altered. The latest version of RSDLite is 6.24.  You may also want to look at House Of Moto 4.1 and see if that is something you want to try.

 

 

1. Confirmed USB 2.0

2. Connected to different 2.0 port

3. Confirmed latest Moto drivers

4. Confirmed latest RSD

5. My first post notes that I tried HouseOfMoto already =)   The only difference is that HouseOfMoto skips to the next image after the first one fails, then moves to the next and fails, then to the next then fails.  RSD halts after the first fail, HouseOfMoto continues on.

 

I appreciate your time.  I suspect that something is happening with the partition access / bootloader, and not allowing anything to be erased or written to them.

[spainter]

1. Confirmed USB 2.0

2. Connected to different 2.0 port

3. Confirmed latest Moto drivers

4. Confirmed latest RSD

5. My first post notes that I tried HouseOfMoto already =)   The only difference is that HouseOfMoto skips to the next image after the first one fails, then moves to the next and fails, then to the next then fails.  RSD halts after the first fail, HouseOfMoto continues on.

 

I appreciate your time.  I suspect that something is happening with the partition access / bootloader, and not allowing anything to be erased or written to them.

We have been seeing more hardware failures the last few months.  There may be a chance to pick up a different main board on ebay.