Related
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
Hi,
after an apparently failed attempt to install the 5.0 OTA update my XT1032 now will boot to a droid lying on its back.
I went to the recovery from there (by pressing VolUp+Power) and did the "factory reset/wipe data" and rebooted.
Same result.
I did "wipe chache". Same result: Droid lying on its back, saying "Kein Befehl" (I guess that means "no command")
I can get into recovery mode (CWM was installed before all this*) so I could try to flash stuff from outside.
But what should I try to flash? I tried flashing a (supposedly) stock system but as soon as I start with "fastboot flash boot boot.img" the phone starts booting again. So I am not really sure what to do now.
Something is seriously wrong with this phone and I would like to restore it to stock settings. I bought it on amazon.DE - so if any one of you guys knows where I could find a truly original stock image for this phone and what to do with it, please let me know.
PS: Right now I can't even get into recovery anymore. The thing just keeps booting and booting. Can't even turn it off.
* meaning: before I flashed the supposed stock recovery that apparently, in combination with the OTA update, got me into this mess
I now followed this guide:
http://forum.xda-developers.com/showthread.php?p=47820707#post47820707
I used option 3b with a 4.4.4 rom ( RETAIL-DE_4.4.4_KXB21.14-L1.40_36_cid7_CFC_1FF )
I excuted all these commands. However, upon flashing the boot.img the phone immediately boots (and gets stuck).
So I re-entered fastboot again to finish the job. Everything else went fine.
But the problem persists: When booting, the phone now displays the "Warning: Bootloader unlocked" message for a long time, with a kind of water ripple effect from bottom to top, repeating.
When I switch it off, it switches back on automatically, trying to boot and getting stuck at this screen. Sometimes I get to the droid lying on its back with a red !-Triangle on top. Poor little bugger. Soft bricked.
What can I do to fix this?
I can still enter fastboot.
I assume that yet again I grabbed the wrong ROM.
Is this supposed to be dead? http://sbf.droid-developers.org/phone.php?device=14
I think you might be on lollipop bootloader as you are having a screen flickering issue & downgrading the boatloader might be dangerous.
I'm don't know whether it will solve your problem but try flashing a lollipop firmware.
I'm not allowed to post links. Google for XT 1032 lollipop firmware. I saw one in groupandroid website.
Download the firmware from the site & execute the given commands.
legolas06 said:
I think you might be on lollipop bootloader as you are having a screen flickering issue & downgrading the boatloader might be dangerous.
I'm don't know whether it will solve your problem but try flashing a lollipop firmware.
I'm not allowed to post links. Google for XT 1032 lollipop firmware. I saw one in groupandroid website.
Download the firmware from the site & execute the given commands.
Click to expand...
Click to collapse
Thank you. I got that file.
"adb devices" won't find my phone, though.
"Fastboot devices" does. So I can't use "adb push ..." to move the ROM to the phone.
Also, whatever option I chose from the Fastboot Flash Mode, the phone starts to boot. So I can not "enter" Recovery.
Should I just use "fastboot update rom.zip"? I don't wan't to miss my last chance to revive this phone.
ADB commands will not work in with the phone fastboot mode.
Since fastboot commands do work, you can manually flash each partition from the stock ROM. Entering recovery isn't required to do this.
fertchen said:
Thank you. I got that file.
"adb devices" won't find my phone, though.
"Fastboot devices" does. So I can't use "adb push ..." to move the ROM to the phone.
Also, whatever option I chose from the Fastboot Flash Mode, the phone starts to boot. So I can not "enter" Recovery.
Should I just use "fastboot update rom.zip"? I don't wan't to miss my last chance to revive this phone.
Click to expand...
Click to collapse
I had similar problems & this method worked for me everytime. Sorry I'm a new user & I cannot post the links.
You can search the forum & find the links.
I found a thread in "xda -> moto g general->[FIRMWARE][XT1032-XT1033] Firmware Lollipop Retail Brasil & Asia 5.0.2" by cristiand391. Download the firmware for your device. It will be in BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml.zip. Extract the contents to the fastboot.exe folder where you use regularly. Run the commands in fastbootmode. Please be careful with the commands.
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_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
Reboot.
audit13 said:
ADB commands will not work in with the phone fastboot mode.
Since fastboot commands do work, you can manually flash each partition from the stock ROM. Entering recovery isn't required to do this.
Click to expand...
Click to collapse
The problem here is that the phone will boot as soon as I flash the boot.img and the whole thing fails.
Do you see a way out of this situation?
Any way to do this with a .zip ROM?
Have you tried flashing different firmware such as the GPE for your phone?
Does boot.img flash properly? If it does, you could try installing TWRP, boot into TWRP, mount the data partition, and use your computer to copy a custom ROM to the phone fpr flashing.
@Fretchen
That might be because you are on lollipop bootloader & you are trying to flash kitkat bootloader?But I may be wrong. Previously you told that you tried restoring to kitkat & that boot.img is kitkat bootloader. Try with this lollipop firmware.
audit13 said:
Have you tried flashing different firmware such as the GPE for your phone?
Does boot.img flash properly? If it does, you could try installing TWRP, boot into TWRP, mount the data partition, and use your computer to copy a custom ROM to the phone fpr flashing.
Click to expand...
Click to collapse
I now did exactly what legolas06 wrote, using "MoeMoe_BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml"
There were "hab check fails" for recovery and boot but at least the device did not reboot upon flashing the boot.img.
I rebooted it and it is going further than ever before, all the Motorola animations were played but in the end the phone got stuck at the circular blue pool (water) with the bit Motorola 'M' plus the concentric water ripple effect.
I switched it off and on again and then it played through the animations, then updated the apps (total number: 9) and then started the system. Apparently it is working.
Thank you very much, I really appreciate your support.
Allow me thse final questions:
Can I from now on just apply OTA updates?
If not, what can I change to make this possible?
Is it advisable to install a EU Rom soon for whatever reason?
fertchen said:
I now did exactly what legolas06 wrote, using "MoeMoe_BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml"
There were "hab check fails" for recovery and boot but at least the device did not reboot upon flashing the boot.img.
I rebooted it and it is going further than ever before, all the Motorola animations were played but in the end the phone got stuck at the circular blue pool (water) with the bit Motorola 'M' plus the concentric water ripple effect.
I switched it off and on again and then it played through the animations, then updated the apps (total number: 9) and then started the system. Apparently it is working.
Thank you very much, I really appreciate your support.
Allow me thse final questions:
Can I from now on just apply OTA updates?
If not, what can I change to make this possible?
Is it advisable to install a EU Rom soon for whatever reason?
Click to expand...
Click to collapse
Happy that I could help.
You flashed the stock firmware so everything should work again. OTA updates if available would work.
fertchen said:
Allow me thse final questions:
Can I from now on just apply OTA updates?
If not, what can I change to make this possible?
Is it advisable to install a EU Rom soon for whatever reason?
Click to expand...
Click to collapse
I don't know if you can apply OTA updates. Before the OTA update will work, you may need to update all Motorol apps via Play store.
You could wait until a fulkl stock lollipop pop is released for your phone and flash it using fastboot.
You can try different ROMs but stick to the ROMs made for your model. I have an xt1032 and I have installed US Retail, stock Telus, and GPE.
worked for me too, thank you soo much. give this solution a try
legolas06 said:
I had similar problems & this method worked for me everytime. Sorry I'm a new user & I cannot post the links.
You can search the forum & find the links.
I found a thread in "xda -> moto g general->[FIRMWARE][XT1032-XT1033] Firmware Lollipop Retail Brasil & Asia 5.0.2" by cristiand391. Download the firmware for your device. It will be in BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml.zip. Extract the contents to the fastboot.exe folder where you use regularly. Run the commands in fastbootmode. Please be careful with the commands.
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_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
Reboot.
Click to expand...
Click to collapse
these steps look soo similar that the ones you can find in other blogs/discussions, but for me, in my case the main difference was the firmware, I tried with a loot of them, but the one that is mentioned in this post, installed smoothly, and with no issues, thank you so much, to post your experience and this solution.
My Best Regards,
Esteban
Hello, I registered, hoping that somone maybe could help here.
Yesterday I wanted to get the latest 5.1 update for my moto g, running 5.0.2. Because I rooted the device amd modified some things like uninstalling system apps and replacing system apps with their updates; I wanted to flash a clean system first. I tried to find a german 5.0.2 rom and couldn't find one, so I decided the 4.4.4 version I got should do the same. So I tried to install it via fastboot. For doing this I used these fastboot commands:
Code:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
I got these three errors: version downgraded primary_gp, version downgraded for tz, version downgraded for boot.
On reboot the phone get's stuck on bootloader unlocked screen and won't boot. I can reset by long pressing power, I can also enter fastboot menu.
After searching for two hours I could find this firmware XT1032_FALCON-RETDE_5.0.2_LXB22.46-28.1_1_cid7_CFC_1FF.xml (can't post link) and tried to install, I used the same commands as above and finished without any error. But there's still the bootloop. I tried to install several times and tried also to wipe data and cache. Can anyone help or is the phone bricked forever?
Dont flash motoboot, i had this same problem when flashing motoboot
I tried it again without flashing motoboot, with the same result. I think the problem is, that I flashed it once, so I think I could only fix it by undoing the motoboot flash.
Edit: Seems like the problem is only with stock rom. I tried to install CM12 and it is running fine, except it refuses a wifi connection. If CM would run that would also be ok, but without wifi,...so I just need stock.
Meanwhile I'm using a custom rom as a workaraound.
Try on this order @piet85
logo
boot
recovery
system.img1
system.img2
system.img3
nhlos
erase midem set 1
erase modem set 2
fsg
erase user data
and cache
Mind that the commands are not written on the right way just because im lazy :-
Thank you a lot, don't get me wrong, but for the moment I'm very glad having a running system on my phone and it runs very good for a custom rom. So there is no real need to flash again. Maybe I will do so, when there are major bugs or when I have more time, but for the moment the custom rom does it's job.
i received an OTA update on friday, i installed it and after it was completed it restarted and now just shows the bootup screen and restarts over and over. i could access recovery but nothing helped eg clearing catche etc so i downloaded Retail Europe (1GB) - XT1541_OSPREY_RETEU_6.0_MPI24.65-33.1_cid7 and followed theses steps
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
every step says it passed ok but when it restarts its still stuck on boot loop the only difference now is if i try to enter recovery it just restarts and again just keeps rebooting.
ive got an aftermarket screen dont know if that makes a difference as ive read apple are bricking phones that havnt been repaired by them selves.
please help im stuck for ideas now
also my bootlocker is locked and cant be unlocked.
just noticed that even though it all pass`s ok my software is staying the same and not updating, ive tried it at least 20 times and on different machines. also tried rsd lite and that also says completed but no change in software
the sotfware listed in the bootloader is, m8919_2020613.22.03.21.29r osprey_emea
and the one im tryig to update to is, m8916_2020629.41.03.21.51r osprey-reteu
bower123456 said:
also my bootlocker is locked and cant be unlocked.
just noticed that even though it all pass`s ok my software is staying the same and not updating, ive tried it at least 20 times and on different machines. also tried rsd lite and that also says completed but no change in software
the sotfware listed in the bootloader is, m8919_2020613.22.03.21.29r osprey_emea
and the one im tryig to update to is, m8916_2020629.41.03.21.51r osprey-reteu
Click to expand...
Click to collapse
Same problem with my Moto 2015 after OTA update, i tryed everything and nothing... =/ boot locked, stock recovery. My baseband M8919_2020613.22.03.21.29R osprey_emea
Tomorrow i will send my moto for Motorola.
wish i could but ive got a replacement screen so they wont touch it so looks like bin for mine
Nothing to do pretty much, same happened to me and there's no fix for that
I think the problem it's the Stock ROM we try flash, because the software version it's different.
I try flash with this ROM [XT1541_OSPREY_RETEU_6.0_MPI24.65-33.1_cid7_subsidy-DEFAULT_CFC__v2.xml], and i could flashing all files without errors, but still looping on motorola logo.
<software_version version="osprey_reteu-user 6.0 MPI24.65-33.1 1 release-keysM8916_2020629.41.03.21.51R"/>
M8919_2020613.22.03.21.29R osprey_emea - Original
if you manage to sort it please let me know
I got an OTA update for marshmallow. At this stage phone was locked, unrooted and not tampered with.
After updating OTA phone went into a bootloop.
'Allow OEM Unlock' is disabled from developer options before even updating OTA so bootloader can't be unlocked.
After bootloop, from bootloader using fastboot (and mfastboot also tried) I flashed "XT1550_OSPREY_RETASIA_DS_2GB_6.0.1_MPI24.107........" this marshmallow firmware using standard commands for newer Moto devies. Even after flashing firmware, still bootloop happens.
Code:
fastboot flash bootloader O:\MotoG3\Firmwares\bootloader.img
fastboot flash logo O:\MotoG3\Firmwares\logo.bin
fastboot flash boot O:\MotoG3\Firmwares\boot.img
fastboot flash recovery O:\MotoG3\Firmwares\recovery.img
fastboot flash system O:\MotoG3\Firmwares\system.img_sparsechunk.0
fastboot flash system O:\MotoG3\Firmwares\system.img_sparsechunk.1
fastboot flash system O:\MotoG3\Firmwares\system.img_sparsechunk.2
fastboot flash system O:\MotoG3\Firmwares\system.img_sparsechunk.3
fastboot flash system O:\MotoG3\Firmwares\system.img_sparsechunk.4
fastboot flash system O:\MotoG3\Firmwares\system.img_sparsechunk.5
fastboot flash system O:\MotoG3\Firmwares\system.img_sparsechunk.6
fastboot flash system O:\MotoG3\Firmwares\system.img_sparsechunk.7
fastboot flash modem O:\MotoG3\Firmwares\NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg O:\MotoG3\Firmwares\fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
pause
At this stage, phone still goes into a bootloop. Clicking on recovery from bootloader also sends phone into a bootloop so can't even access stock recovery.
Also no way to erase system as bootloader is locked.
In bootloader some details are given:
baseband- M8916_2020617.29.03.21.45R OSPREY_APAC_CUST
product- osprey xt1550 16gb p2b
cpu- msm8916
device is locked. status code 0. software status official.
How do I get the phone back in working state?
Other bootloop guides were not useful as here even after flashing stock firmware phone still goes into a bootloop. ALso no stock recovery is accessible and BL is locked
Using the guide in http://forum.xda-developers.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750, it is suposed to work (but you can't enter in stock recovery to do a factory reset, right?).
Try one more time, and confirme you flash all the system.img_sparechunk's files (some firmware images have less, and some have more).
In the first boot, the device can take a long period of time to boot (10-15 min in some cases).
If you can boot the recovery or the system, do a factory reset.
did you get it working?