Post Reply Subscribe to Thread Email Thread

Unhappy DROID MAXX stuck at Motorola screen/fastboot "Boot up failed"

24th September 2014, 12:30 AM   |  #1  
OP Member
Thanks Meter: 25
 
66 posts
Join Date:Joined: Feb 2008
More
Huy guys, very strange issue on my XT1080M.

I stopped using this phone a couple of months ago when I got my Moto X and then work provided me with a different device. The phone went dead at some point, and now, even after plugging it in and letting it charge, it will NOT boot up. It will not progress past the Motorola screen. The screen comes on, it vibrates, and then it gets stuck. The Moto logo is the same color every single time (purple) instead of changing.. thought that was interesting.

The phone had a pending software update that I never took, and I wonder if something prompted it to actually start the update instead. Either way, I downloaded the 4.4.4 fxz files and flashed it in RSDLite. The flashing went through successfully, but it still will not boot. Fastboot is accessible, but if you pick "Recovery", it shows the Moto logo, then comes back to the Fastboot screen and says "Boot up failed".

I re-downloaded and reflashed the files thinking maybe something is corrupt, but it still won't boot.

I really hate to lose this phone as it'd be really great to have as a backup, but I'm really out of any ideas. Bootloader is locked. Device was originally rooted and "security unlocked" with rockmymoto and whatever the security off program was (it's been a while..)

Any ideas at all?
24th September 2014, 12:34 AM   |  #2  
Topsnake's Avatar
Senior Member
Thanks Meter: 569
 
1,077 posts
Join Date:Joined: Jan 2011
Donate to Me
More
Quote:
Originally Posted by digitaloutsider

Huy guys, very strange issue on my XT1080M.

I stopped using this phone a couple of months ago when I got my Moto X and then work provided me with a different device. The phone went dead at some point, and now, even after plugging it in and letting it charge, it will NOT boot up. It will not progress past the Motorola screen. The screen comes on, it vibrates, and then it gets stuck. The Moto logo is the same color every single time (purple) instead of changing.. thought that was interesting.

The phone had a pending software update that I never took, and I wonder if something prompted it to actually start the update instead. Either way, I downloaded the 4.4.4 fxz files and flashed it in RSDLite. The flashing went through successfully, but it still will not boot. Fastboot is accessible, but if you pick "Recovery", it shows the Moto logo, then comes back to the Fastboot screen and says "Boot up failed".

I re-downloaded and reflashed the files thinking maybe something is corrupt, but it still won't boot.

I really hate to lose this phone as it'd be really great to have as a backup, but I'm really out of any ideas. Bootloader is locked. Device was originally rooted and "security unlocked" with rockmymoto and whatever the security off program was (it's been a while..)

Any ideas at all?

Which FXZ did you actually flash? Go through and manually flash the FXZ and see what happens. Also run an md5 check on the FXZ
24th September 2014, 12:59 AM   |  #3  
OP Member
Thanks Meter: 25
 
66 posts
Join Date:Joined: Feb 2008
More
Okay, manually flashed it using mfastboot. No difference. Still stuck on the purple Moto logo.

FXZ file used was 1FF-obake-maxx_verizon-user-4.4.4-SU4.21-release-keys.xml.zip from sbf.droid-developers.org.

These are the steps that I used:

mfastboot getvar max-download-size
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot reboot-bootloader
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot

MD5 matched. Argh.
24th September 2014, 01:44 AM   |  #4  
Topsnake's Avatar
Senior Member
Thanks Meter: 569
 
1,077 posts
Join Date:Joined: Jan 2011
Donate to Me
More
Quote:
Originally Posted by digitaloutsider

Okay, manually flashed it using mfastboot. No difference. Still stuck on the purple Moto logo.

FXZ file used was 1FF-obake-maxx_verizon-user-4.4.4-SU4.21-release-keys.xml.zip from sbf.droid-developers.org.

These are the steps that I used:

mfastboot getvar max-download-size
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot reboot-bootloader
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot

MD5 matched. Argh.

Well im out of suggestions. May be bricked
24th September 2014, 04:43 AM   |  #5  
Senior Member
Thanks Meter: 534
 
2,639 posts
Join Date:Joined: Sep 2012
Quote:
Originally Posted by digitaloutsider

Huy guys, very strange issue on my XT1080M.

I stopped using this phone a couple of months ago when I got my Moto X and then work provided me with a different device. The phone went dead at some point, and now, even after plugging it in and letting it charge, it will NOT boot up. It will not progress past the Motorola screen. The screen comes on, it vibrates, and then it gets stuck. The Moto logo is the same color every single time (purple) instead of changing.. thought that was interesting.

The phone had a pending software update that I never took, and I wonder if something prompted it to actually start the update instead. Either way, I downloaded the 4.4.4 fxz files and flashed it in RSDLite. The flashing went through successfully, but it still will not boot. Fastboot is accessible, but if you pick "Recovery", it shows the Moto logo, then comes back to the Fastboot screen and says "Boot up failed".

I re-downloaded and reflashed the files thinking maybe something is corrupt, but it still won't boot.

I really hate to lose this phone as it'd be really great to have as a backup, but I'm really out of any ideas. Bootloader is locked. Device was originally rooted and "security unlocked" with rockmymoto and whatever the security off program was (it's been a while..)

Any ideas at all?

Why don't you flash the XML with RSD lite, the 444 has no getvar or erase userdata lines in it.
24th September 2014, 05:22 AM   |  #6  
Topsnake's Avatar
Senior Member
Thanks Meter: 569
 
1,077 posts
Join Date:Joined: Jan 2011
Donate to Me
More
Quote:
Originally Posted by aviwdoowks

Why don't you flash the XML with RSD lite, the 444 has no getvar or erase userdata lines in it.

He did. Look at the post you just quoted.
24th September 2014, 05:39 AM   |  #7  
Senior Member
Thanks Meter: 26
 
154 posts
Join Date:Joined: Dec 2007
Same problem here. Rebooted one day, never booted back up. Can't get the phone to charge enough to even complete most flashing commands.
25th September 2014, 10:54 PM   |  #8  
OP Member
Thanks Meter: 25
 
66 posts
Join Date:Joined: Feb 2008
More
Well, I was able to get my hands on another DROID MAXX. Unfortunately, this one already has 4.4.4 so I'm screwed for being able to use Sunshine until some sort of 4.4.4 root comes out. Plus, the device is a 2013 model, so I can't get a BL code from that Chinese guy.

Sigh. Such is life!
26th September 2014, 02:05 PM   |  #9  
Senior Member
Thanks Meter: 27
 
232 posts
Join Date:Joined: Nov 2011
Quote:
Originally Posted by digitaloutsider

Well, I was able to get my hands on another DROID MAXX. Unfortunately, this one already has 4.4.4 so I'm screwed for being able to use Sunshine until some sort of 4.4.4 root comes out. Plus, the device is a 2013 model, so I can't get a BL code from that Chinese guy.

Sigh. Such is life!

Can you flash a custom recovery and get it to boot to that using the broken device?
26th September 2014, 06:13 PM   |  #10  
OP Member
Thanks Meter: 25
 
66 posts
Join Date:Joined: Feb 2008
More
The old one had a locked bootloader.

Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes