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?
digitaloutsider said:
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?
Click to expand...
Click to collapse
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
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.
digitaloutsider said:
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.
Click to expand...
Click to collapse
Well im out of suggestions. May be bricked
digitaloutsider said:
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?
Click to expand...
Click to collapse
Why don't you flash the XML with RSD lite, the 444 has no getvar or erase userdata lines in it.
aviwdoowks said:
Why don't you flash the XML with RSD lite, the 444 has no getvar or erase userdata lines in it.
Click to expand...
Click to collapse
He did. Look at the post you just quoted.
Same problem here. Rebooted one day, never booted back up. Can't get the phone to charge enough to even complete most flashing commands.
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!
digitaloutsider said:
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!
Click to expand...
Click to collapse
Can you flash a custom recovery and get it to boot to that using the broken device?
The old one had a locked bootloader.
Have you tried house of moto to flash yet?
what system version were you on prior to having problems?
I ran into this same issue and never recovered from it. I had an unlocked bootloader prior to attempting to recover. Now it fails to boot and shows the boot loader is now locked.
my moto x fails to boot up and shows no command when I boot up the phone. Fastboot shows boot up failed
I have one that's having a similar issue. Shows the Motorola logo then nothing. Stock ROM and nothing modified.
Edit: It's a Verizon model (If that has any bearing)
So is there no fix to this issue? I tried to flash a custom recovery using fastboot and got stuck in fastboot mode because the image was too large, and failure to flash.
Also now adb can't find the device
motorola droid max stuck black screen at BLBROKE. help me
Hello. So I've restored my old XT1032 to 5.1 stock and locked the bootloader again but I'm still getting the unlocked bootloader warning message when booting. I've tried to reflash the logo.bin but that didn't work.
Any ideas?
Thanks
flash the logo.bin from here:
http://forum.xda-developers.com/showthread.php?t=2548530
and then it will go away. Motorola did this beacuse the bootloader was unlocked before and relock it doesn't bring back the original boot logo. In bootloader mode you can see that you have now STATUS CODE: 2 instead of 0 when never was unlocked.
Hi everybody,
I need your help for some informations...
I make a custom boot animation (zip file) but my phone is locked and I don't want unlock or root just for this.
So I throught make a binary and flash logo with fastboot (e.g fastboot flash logo logo.bin).
Is It possible? If not have you another solution? Copy/Paste my zip file without su? Or root temporarily with adb...
FYI: This is for several phones, not just one, so get unlock code from Motorola is excluded in my case.
Thanks for your help
Is it a bootlogo or boot animation? Logo.bin is the static image and boot animation needs a zip file to be placed in system (that needs root access obviously). You can't merge boot animation and boot logo to logo.bin .
Broadcasted from Zeta Reticuli
It's a boot animation.
OK, so I need to unlock bootloader for a root access....
I will put a static image.
Thanks for your help
So I got bored of previous ctOS boot logo so I decided to make my own one. This comes with the battery images, logo.bin (unlocked bootloader) and logo.bin (locked bootloader) assuming that you flash this at the start of a new complete flash with a system. Otherwise just extract logo.bin from the zip on your desktop and use fastboot with "fastboot flash logo logo.bin" command to flash it. It would be nice to have some feedback but, please be patient with me I am new to this. I will be posting screenshots below in a bit with the flashable zip. The first image is the boot logo that should appear with a locked bootloader and the second image is the boot logo that should appear with a unlocked bootloader.
Note: When the phone boots the images are in legible quality and there are no white borders. :Note
Hi all -
I have committed a stupid typo that has locked up my device: I just unlocked my bootloader and everything was working fine. I wanted to change the boot image so I don't get the "Bad Key" message at the bottom of the initial boot screen.
Unfortunately, in fastboot mode I typed:
Code:
fastboot flash boot logo.bin
instead of
Code:
fastboot flash logo_a logo.bin
Now a normal system boot fails and the device goes into fastboot with the message "Invalid boot image size! failed to validate boot image"
I am able to boot to TWRP by issuing the command
Code:
fastboot boot twrp-3.5.0_9-0-river.img
but I have no idea what to do after that.
How do I fix this?
After finding this thread:
Back to Stock & ReLock Boot Loader (Google Fi)
I wound up getting the $150 deal from google for the G7, had massive issues with the phone, so back to google with it. If you are curious the issues I had included: Speaker would randomly stop working, seriously I'd reboot, it would work, the...
forum.xda-developers.com
I have a possible path forward.
I am downloading the XT1962-1_RIVER_RETUS_9.0_PPO29.114-16_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip file (it's huge).
Then I will then extract the boot.img file and do a
Code:
fastboot flash boot boot.img
and see what happens.
Edit: I will wait a while first and see if any gurus have some better advice
I ended up just doing a factory reset from fastboot.