Support Discontinued.
Is it possible to get the original boot image for the Droid Maxx to replace the unlocked bootloader warning
Sent from my XT1080 using Tapatalk
nubia11 said:
Is it possible to get the original boot image for the Droid Maxx to replace the unlocked bootloader warning
Sent from my XT1080 using Tapatalk
Click to expand...
Click to collapse
Ive tried with no success. This is the simplest method available.
Topsnake said:
Ive tried with no success. This is the simplest method available.
Click to expand...
Click to collapse
Got it... I will take your advice on this... Much appreciated!
Check your pm's
Sent from my XT1080 using Tapatalk
Do we know details on how to make our own logos yet? Dimension limits, logo.bin offsets?
logo.bin did not work for me... i just got a tan screen w pixelated square.
Flashing original logo.bin from FXZ restored me to the original warning.... I wonder how come flashing that file does not restore original boot logo.
asuhoops8628 said:
logo.bin did not work for me... i just got a tan screen w pixelated square.
Flashing original logo.bin from FXZ restored me to the original warning.... I wonder how come flashing that file does not restore original boot logo.
Click to expand...
Click to collapse
Possible bad download. Redownload and try again. I just verified the file to be correct
Droid Maxx "Developer Edition"
Same problem man. Idk what is up. I downloaded fresh, unrar'd, copied logo.bin to my ADB root folder and flashed.
Still getting the tan screen with garbled square.
asuhoops8628 said:
Same problem man. Idk what is up. I downloaded fresh, unrar'd, copied logo.bin to my ADB root folder and flashed.
Still getting the tan screen with garbled square.
Click to expand...
Click to collapse
flashed successfully on my maxx
Topsnake said:
Possible bad download. Redownload and try again. I just verified the file to be correct
Droid Maxx "Developer Edition"
Click to expand...
Click to collapse
BladeRunner said:
flashed successfully on my maxx
Click to expand...
Click to collapse
Any way to erase the "logo" area before the flash? This time I got half garbled image and the bottom half was the remainder of the unlocked bl message.
This is my adb commands
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash logo logo.bin
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'logo' (636 KB)...
OKAY [ 0.199s]
writing 'logo'...
OKAY [ 0.748s]
finished. total time: 0.949s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot
rebooting...
finished. total time: 0.002s
asuhoops8628 said:
Any way to erase the "logo" area before the flash? This time I got half garbled image and the bottom half was the remainder of the unlocked bl message.
This is my adb commands
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash logo logo.bin
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'logo' (636 KB)...
OKAY [ 0.199s]
writing 'logo'...
OKAY [ 0.748s]
finished. total time: 0.949s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot
rebooting...
finished. total time: 0.002s
Click to expand...
Click to collapse
Im not sure what the deal is but the file you are flashing seems a little small IIRC. Try a different unrar method? I can't recreate the issue you are having.
Droid Maxx "Developer Edition"
Topsnake said:
Im not sure what the deal is but the file you are flashing seems a little small IIRC. Try a different unrar method? I can't recreate the issue you are having.
Droid Maxx "Developer Edition"
Click to expand...
Click to collapse
Hmm, I am using WinRar. What should be the appropriate Filesize?
EDIT:
I also see that when I unrar, i get 637kb filesize, but when flashing only 636kb....
asuhoops8628 said:
Hmm, I am using WinRar. What should be the appropriate Filesize?
EDIT:
I also see that when I unrar, i get 637kb filesize, but when flashing only 636kb....
Click to expand...
Click to collapse
I extracted mine with 7zip
Sent from my XT1080 using Tapatalk
BladeRunner said:
I extracted mine with 7zip
Sent from my XT1080 using Tapatalk
Click to expand...
Click to collapse
still nothing... i give up... this mod is not destined to work on my maxx
asuhoops8628 said:
still nothing... i give up... this mod is not destined to work on my maxx
Click to expand...
Click to collapse
Try fastboot erase logo and fastboot erase clogo before flashing
Sent from my XT1080 using Tapatalk
BladeRunner said:
Try fastboot erase logo and fastboot erase clogo before flashing
Sent from my XT1080 using Tapatalk
Click to expand...
Click to collapse
failboat.jpg again. I got a permission denied from the bootloader when trying to erase logo. clogo went ok.
asuhoops8628 said:
failboat.jpg again. I got a permission denied from the bootloader when trying to erase logo. clogo went ok.
Click to expand...
Click to collapse
I'm stumped. That's weird. So far you are the only one to have an issue. I've reflashed 6 times already trying to recreate the issue
Droid Maxx "Developer Edition"
I've just flashed mine and it works just fine. That is much better than warning window, but I would love to have a black background and more droid-style logo =)))
Are we aware of the format? Is there a tool to build a custom logo?
I've compared original logo.bin to this one and considering that image is in RAW fromat (means not compressed) I concluded that I'd rather roll back to the original droid maxx logo. DROID MAXX's logo is 2,625,328 bytes while this mod is 561720 bytes. It means that something might be missing like charge battery icon, etc. I'll try to play with the original file.
---------- Post added at 03:38 PM ---------- Previous post was at 03:28 PM ----------
I can confirm that there are 3 images (with special headers and markers) in the original MAXX logo file.
first is at offset 512 sized 540x540 (original logo with locked bootloader)
second is at offset 875520 sized 540x540 (empty battery with flash and 0% text)
third is at 1750528 sized 540x540 (warning text)
I'll try to modify tho original file and just copy over part 1 to part 3 (replace warning with original image) and flash. I post a proper file if succeed.
This will be the first step to the full custom logo. =)
i tried digging into the logo.bin file myself. I found this thread over on the moto g section and it required some hex editing. i attempted it myself but not quite sure if i changed the correct offsets. When i flashed it all i got was a black logo and bootloop. I eventually flashed the original logo.bin and phone boots up like normal. maybe some of the developers would have better luck than i did
Related
Hello dear friends!
I have a problem with my Atrix HD. I have problems to flash the boot.img and the system.img.
I tried with RSD Lite, Myth Tools - AHD, Fastboot flash and none have been able to flash it. I downloaded all drivers!
may be permanent brick?
The only thing I shows Battery Low, Battery OK sometimes.
I saw on some forums that the "Factory Cable" has the possibility to flash my phone.
What are the chances of coming back to life my MB886?
Here the details of what I show!
AP Fastboot Flash Mode (s)
10.9b (*) (sha-2e68372, 2012-11-17 23:33:08)
eMMC Info: Size 8GB
Device is LOCKED, Status code: 0
Low Battery
USB Connect
Data Cable
Partition (boot) Downgraded Security Version
Fastboot Reason: Boot Failure.
Waiting for your prompt help
Thank you.
Greetings!
adal_elfather said:
Hello dear friends!
I have a problem with my Atrix HD. I have problems to flash the boot.img and the system.img.
I tried with RSD Lite, Myth Tools - AHD, Fastboot flash and none have been able to flash it. I downloaded all drivers!
may be permanent brick?
The only thing I shows Battery Low, Battery OK sometimes.
I saw on some forums that the "Factory Cable" has the possibility to flash my phone.
What are the chances of coming back to life my MB886?
Here the details of what I show!
AP Fastboot Flash Mode (s)
10.9b (*) (sha-2e68372, 2012-11-17 23:33:08)
eMMC Info: Size 8GB
Device is LOCKED, Status code: 0
Low Battery
USB Connect
Data Cable
Partition (boot) Downgraded Security Version
Fastboot Reason: Boot Failure.
Waiting for your prompt help
Thank you.
Greetings!
Click to expand...
Click to collapse
nothing to panic... hold power+vol up+vol down to power your device off and put it to charge (do not charge with pc/laptop, use a AC power source)
after an hour, follow these steps..
1)download the required firmware from here and fastboot binaries
2)extract the zip and place downloaded fastboot binaries in the extracted directory and open terminal in this directory.
3)type the following commands in order
fastboot flash modem NON-HLOS.bin
fastboot flash boot boot.img
fastboot flash devtree device_tree.bin
fastboot flash system system.img
fastboot -w
fastboot erase cache
fastboot reboot
Click to expand...
Click to collapse
Many Thanks for your help.
I tried to, but I have always problems with Flash.
when flashing the NON-HLOS, there is no problem.
but when I'm flashing the boot.img always gives me this problem.
sending 'boot' (10240 KB) ...
OKAY [0.833s]
writing 'boot' ...
Preflash validation failed
FAILED (remote failure)
finished. Total time: 1.124s
and when I try the system.img
sending 'system' (30720 KB) ...
OKAY [2.506s]
writing 'system' ...
Preflash validation failed
FAILED (remote failure)
finished. Total time: 2.842s
and on the phone adds the following:
Partition (Boot) Security Version Downgraded
preflash validation failed for boot
Partition (System) Security Version Downgraded
PIV validation for system block failed
Invalid PIV image: system
What is Security Version Downgraded?
What is PIV?
Again, thank you very much for the help.
waiting for comments
regards
adal_elfather said:
Many Thanks for your help.
I tried to, but I have always problems with Flash.
when flashing the NON-HLOS, there is no problem.
but when I'm flashing the boot.img always gives me this problem.
sending 'boot' (10240 KB) ...
OKAY [0.833s]
writing 'boot' ...
Preflash validation failed
FAILED (remote failure)
finished. Total time: 1.124s
and when I try the system.img
sending 'system' (30720 KB) ...
OKAY [2.506s]
writing 'system' ...
Preflash validation failed
FAILED (remote failure)
finished. Total time: 2.842s
and on the phone adds the following:
Partition (Boot) Security Version Downgraded
preflash validation failed for boot
Partition (System) Security Version Downgraded
PIV validation for system block failed
Invalid PIV image: system
What is Security Version Downgraded?
What is PIV?
Again, thank you very much for the help.
waiting for comments
regards
Click to expand...
Click to collapse
What firmware are you trying to flash?
Sent from my MB886 using xda app-developers app
Aingaran said:
What firmware are you trying to flash?
Sent from my MB886 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the help.
I tried with all 3 of ATT & T. Currently I am trying to "MB886_att-user-4.1.1-9.8.0Q-97_MB886_FFW-20-27-release-keys-ATT-US_BuildA.xml.zip"
Jelly Bean 4.1.1
but with the other 2 (ICS) always send me the same error.
Waiting for your comments
thanks
regards
adal_elfather said:
Thanks for the help.
I tried with all 3 of ATT & T. Currently I am trying to "MB886_att-user-4.1.1-9.8.0Q-97_MB886_FFW-20-27-release-keys-ATT-US_BuildA.xml.zip"
Jelly Bean 4.1.1
but with the other 2 (ICS) always send me the same error.
Waiting for your comments
thanks
regards
Click to expand...
Click to collapse
Try Mexican retail... Last hope... Is your boot loader locked? If so, that may be the reason... Is your phone working... Any ROM inside it?
Sent from my MB886 using xda app-developers app
Aingaran said:
Try Mexican retail... Last hope... Is your boot loader locked? If so, that may be the reason... Is your phone working... Any ROM inside it?
Sent from my MB886 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the help.
My phone is AT&T and had no unlocked bootloader or modified roms.
regards
adal_elfather said:
Thanks for the help.
My phone is AT&T and had no unlocked bootloader or modified roms.
regards
Click to expand...
Click to collapse
Is your phone working with that att ROM now? Or have you messes up with anything...
Sent from my MB886 using xda app-developers app
Aingaran said:
Is your phone working with that att ROM now? Or have you messes up with anything...
Sent from my MB886 using xda app-developers app
Click to expand...
Click to collapse
Not work.
Fastboot load only. that's all it does
adal_elfather said:
Not work.
Fastboot load only. that's all it does
Click to expand...
Click to collapse
what happend to the stock rom? what did you do?
Aingaran said:
what happend to the stock rom? what did you do?
Click to expand...
Click to collapse
I tried to install ZIP from SD card and this was the result.
I already tried flash the 3 firmware stock from AT&T and the Mexican. With all is same result.
Can you get to fastboot mode? Unlock the bootloader and flash stock.
Sent from my PACMAN MATRIX HD MAXX
adal_elfather said:
I tried to install ZIP from SD card and this was the result.
I already tried flash the 3 firmware stock from AT&T and the Mexican. With all is same result.
Click to expand...
Click to collapse
What ROM is that? That you flashed from stock recovery?
Sent from my MB886 using xda app-developers app
---------- Post added at 10:53 PM ---------- Previous post was at 10:46 PM ----------
adal_elfather said:
Not work.
Fastboot load only. that's all it does
Click to expand...
Click to collapse
deeje00 said:
Can you get to fastboot mode? Unlock the bootloader and flash stock.
Sent from my PACMAN MATRIX HD MAXX
Click to expand...
Click to collapse
how will you unlock your bootloader only with fastboot?!! if that is possible, please give that link, it will help him a lot
deeje00 said:
Can you get to fastboot mode? Unlock the bootloader and flash stock.
Sent from my PACMAN MATRIX HD MAXX
Click to expand...
Click to collapse
Yes, I can get Fastboot mode.
How to unlock the bootloader in fastboot?
Thanks!
Well with any luck your computer might find your phone in the root program so you can root and then unlock.
Sent from my PACMAN MATRIX HD MAXX
Aingaran said:
Try Mexican retail... Last hope... Is your boot loader locked? If so, that may be the reason... Is your phone working... Any ROM inside it?
Sent from my MB886 using xda app-developers app
Click to expand...
Click to collapse
I tried, but the result is no longer the same.
Try using this to root and then unlock.
http://forum.xda-developers.com/showthread.php?t=2262726
Make sure to install the drivers first.
Sent from my PACMAN MATRIX HD MAXX
deeje00 said:
Well with any luck your computer might find your phone in the root program so you can root and then unlock.
Sent from my PACMAN MATRIX HD MAXX
Click to expand...
Click to collapse
I saw that to unlock the bootloader need to be root, you got marked unknown sources. and that I can not do with the phone bricked.
Could you please send me a program or application with which I can do with the phone brick?
Thanks for the help.
deeje00 said:
Try using this to root and then unlock.
http://forum.xda-developers.com/showthread.php?t=2262726
Make sure to install the drivers first.
Sent from my PACMAN MATRIX HD MAXX
Click to expand...
Click to collapse
Ok, thanks, I will try.
Then I notify
deeje00 said:
Try using this to root and then unlock.
http://forum.xda-developers.com/showthread.php?t=2262726
Make sure to install the drivers first.
Sent from my PACMAN MATRIX HD MAXX
Click to expand...
Click to collapse
I tried to unlock the bootloader, but I can not do it.
I get the following message in the application and nothing happens!
I'm on the T-Mobile variant and have followed the steps on the motorola website to unlock the bootloader. When I boot into fastboot, it says the device is unlocked with at status code 3. When I run 'fastboot flash recovery recovery.img' everything seems to run fine:
fastboot flash recovery recovery.img
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'recovery' (10240 KB)...
OKAY [ 0.827s]
writing 'recovery'...
OKAY [ 1.102s]
finished. total time: 1.930sWhen I try to reboot into recovery mode it just shows me the warning that my bootloader is unlocked, then boots as normal. I don't know what to do. I've tried both the twrp and cwm recovery images. Any help?
what recovery did you flash?
waiflih said:
what recovery did you flash?
Click to expand...
Click to collapse
I've tried both the twrp and cwm recoveries that are available in the android development section.
You are replacing recovery.img with the actual file name right?
Sent from my Moto X.
mentose457 said:
You are replacing recovery.img with the actual file name right?
Sent from my Moto X.
Click to expand...
Click to collapse
Yup. From reading around it seems like there's a script in /system that flashes the stock recovery upon booting up. I tried to get the PwnMyMoto apk onto my device to get root and remove the recovery script file but now I'm getting an unexpected exception when trying to install the apk through adb. I have both USB debugging and Unknown Sources allowed. Any ideas?
Edit:
By the way I am T-Mobile, post OTA. If that changes anything.
elijahah said:
Yup. From reading around it seems like there's a script in /system that flashes the stock recovery upon booting up. I tried to get the PwnMyMoto apk onto my device to get root and remove the recovery script file but now I'm getting an unexpected exception when trying to install the apk through adb. I have both USB debugging and Unknown Sources allowed. Any ideas?
Edit:
By the way I am T-Mobile, post OTA. If that changes anything.
Click to expand...
Click to collapse
This might be a long way to do it but can't you downgrade back to 4.2.2 then get root with that then follow the instructions found in the general section for maintaining root through taking the ota? This should fix your problem. Also the instructions there might give you a different idea of how to work around this issue. You might just be able to flash the boot image and install the hidden su yourself.
Sent from my XT1060 using xda app-developers app
jayboyyyy said:
This might be a long way to do it but can't you downgrade back to 4.2.2 then get root with that then follow the instructions found in the general section for maintaining root through taking the ota? This should fix your problem. Also the instructions there might give you a different idea of how to work around this issue. You might just be able to flash the boot image and install the hidden su yourself.
Sent from my XT1060 using xda app-developers app
Click to expand...
Click to collapse
I'm already on 4.2.2. I'm guessing you mean to undo the recent OTA? How would I do that without a custom recovery or root?
Twrp has a built on file explorer, can you boot directly into recovery from the fastboot screen and delete the file that way?
Sent on my Moto X
flashallthetime said:
Twrp has a built on file explorer, can you boot directly into recovery from the fastboot screen and delete the file that way?
Sent on my Moto X
Click to expand...
Click to collapse
Unfortunately I can't I flash the recovery via fastboot then try to boot into recovery and it just shows me the warning that my bootloader is unlocked and boots normally.
elijahah said:
Unfortunately I can't I flash the recovery via fastboot then try to boot into recovery and it just shows me the warning that my bootloader is unlocked and boots normally.
Click to expand...
Click to collapse
One more clarification: After you flash recovery, you are using the volume down key to highlight recovery and then you are using the up arrow to select it correct? You do not press the power button to make the selection as on nexus devices.
elijahah said:
Unfortunately I can't I flash the recovery via fastboot then try to boot into recovery and it just shows me the warning that my bootloader is unlocked and boots normally.
Click to expand...
Click to collapse
Don't flash it, boot it. Fastboot boot recovery recovery.IMG. if that works maybe you can delete that file.
Sent from my Nexus 7
mentose457 said:
One more clarification: After you flash recovery, you are using the volume down key to highlight recovery and then you are using the up arrow to select it correct? You do not press the power button to make the selection as on nexus devices.
Click to expand...
Click to collapse
Oops I didn't know that! Still no avail. I get a screen with the green android that says 'no command'
phositadc said:
Don't flash it, boot it. Fastboot boot recovery recovery.IMG. if that works maybe you can delete that file.
Sent from my Nexus 7
Click to expand...
Click to collapse
Ah man I thought this would work but this is the response I got:
fastboot boot twrp263.img
downloading 'boot.img'...
OKAY [ 0.811s]
booting...
(bootloader) Command restricted
FAILED (remote failure)
finished. total time: 0.881s
Thanks for all your help though guys.
elijahah said:
Oops I didn't know that! Still no avail. I get a screen with the green android that says 'no command'
Ah man I thought this would work but this is the response I got:
fastboot boot twrp263.img
downloading 'boot.img'...
OKAY [ 0.811s]
booting...
(bootloader) Command restricted
FAILED (remote failure)
finished. total time: 0.881s
Thanks for all your help though guys.
Click to expand...
Click to collapse
Did you leave a word out? I think it's fastboot boot recovery recovery. IMG.
Sent from my Nexus 7
elijahah said:
Oops I didn't know that! Still no avail. I get a screen with the green android that says 'no command'
Thanks for all your help though guys.
Click to expand...
Click to collapse
Erase the recovery partition. Then try flashing twrp.
fastboot erase recovery
fastboot flash recovery twrp26XX.img
Sent from my Moto X.
mentose457 said:
Erase the recovery partition. Then try flashing twrp.
fastboot erase recovery
fastboot flash recovery twrp26XX.img
Sent from my Moto X.
Click to expand...
Click to collapse
I get this:
fastboot erase recovery
(bootloader) Variable not supported!
erasing 'recovery'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.071s
Actually it works now. I just tired fastboot flash recovery twrp263.img then pressed vol down to get to recovery and pressed vol up to select it and it worked! Thanks for sticking with me guys.
elijahah said:
Actually it works now. I just tired fastboot flash recovery twrp263.img then pressed vol down to get to recovery and pressed vol up to select it and it worked! Thanks for sticking with me guys.
Click to expand...
Click to collapse
Excellent. Glad you got it working.
elijahah said:
Actually it works now. I just tired fastboot flash recovery twrp263.img then pressed vol down to get to recovery and pressed vol up to select it and it worked! Thanks for sticking with me guys.
Click to expand...
Click to collapse
PS you had recovery the first time you hit the up volume and it sent you to a screen that said "no command" from that screen if you press the up volume and power button together it sends you to the recovery screen. It may be down volume and power together to get passed that "no command" screen but its one of the two. I saw people having that same problem in the forum about maintaining root through the OTA.
phositadc said:
Did you leave a word out? I think it's fastboot boot recovery recovery. IMG.
Sent from my Nexus 7
Click to expand...
Click to collapse
elijahah said:
Oops I didn't know that! Still no avail. I get a screen with the green android that says 'no command'
Ah man I thought this would work but this is the response I got:
fastboot boot twrp263.img
downloading 'boot.img'...
OKAY [ 0.811s]
booting...
(bootloader) Command restricted
FAILED (remote failure)
finished. total time: 0.881s
Thanks for all your help though guys.
Click to expand...
Click to collapse
Probably your battery isnt charged enough to proceed with operation.
Check your battery and make sure it is charged at least 50% and try again.
leonardoafa said:
Probably your battery isnt charged enough to proceed with operation.
Check your battery and make sure it is charged at least 50% and try again.
Click to expand...
Click to collapse
Will charge up a bit over 50% and see. I still get permission denied. Plus when I try to get into recovery, I can't. The Motorola log shows up for a while, then restarts and boots normally into Android.
Unfortunately I loaded the leaked Lollipop build to my PE and it was working great, but I wanted to get on the soak test build. I downloaded the stock KK 4.4.4 system image from Motorola in order to restore before updated to soak test. All but one of the files flashes fine, the exception being motoboot.img. I get Preflash validation failed error for that file.
The phone boots and runs but the missing file means the update won't install. Does anyone have any thoughts on how to restore this file?
TMO_21.21.42.victara_tmo.tmo.en.US>mfastboot flash boot motoboot.img
target max-sparse-size: 256MB
sending 'boot' (2022 KB)...
OKAY [ 0.089s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.109s
samabuelsamid said:
Unfortunately I loaded the leaked Lollipop build to my PE and it was working great, but I wanted to get on the soak test build. I downloaded the stock KK 4.4.4 system image from Motorola in order to restore before updated to soak test. All but one of the files flashes fine, the exception being motoboot.img. I get Preflash validation failed error for that file.
The phone boots and runs but the missing file means the update won't install. Does anyone have any thoughts on how to restore this file?
TMO_21.21.42.victara_tmo.tmo.en.US>mfastboot flash boot motoboot.img
target max-sparse-size: 256MB
sending 'boot' (2022 KB)...
OKAY [ 0.089s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.109s
Click to expand...
Click to collapse
try:
Code:
mfastboot flash motoboot motoboot.img
holtenc said:
try:
Code:
mfastboot flash motoboot motoboot.img
Click to expand...
Click to collapse
Sorry, copy/paste error there.
I actually tried the motoboot motoboot.img too and get the same error.
well I'm not sure then man. I guess all I can suggest is follow THESE instructions to a T.
also if you have flashed any of the radios floating around these forums insert "fastboot flash modem radio.img" in there somewhere.
And of course make sure your bootloader is unlocked.
holtenc said:
well I'm not sure then man. I guess all I can suggest is follow THESE instructions to a T.
also if you have flashed any of the radios floating around these forums insert "fastboot flash modem radio.img" in there somewhere.
And of course make sure your bootloader is unlocked.
Click to expand...
Click to collapse
Thanks, those are precisely the instructions I used. I haven't done anything with the radios. I flashed the leaked lollipop rom and then used the official image files to try to go back. The bootloader was initially not unlocked, I unlocked it only in an attempt to get the motoboot file to flash. Now I can't relock it because this part of the image is missing.
Have you tried re-doing all those instructions from the top with your bootloader unocked? instead of just trying to reflash motoboot?
I'm surprised it let your flash somethings while your bootloader was still locked.
holtenc said:
Have you tried re-doing all those instructions from the top with your bootloader unocked? instead of just trying to reflash motoboot?
I'm surprised it let your flash somethings while your bootloader was still locked.
Click to expand...
Click to collapse
Only thing I did with bootloader locked was the partition. As soon as I got to the motoboot and it failed, I figured I would need to unlock and did that. Since then, I've tried the whole process a couple of times with the same result. I will however, give it another shot.
You don't need motoboot to update. Go use the script and it will do everything for you.
tw1tch175 said:
You don't need motoboot to update. Go use the script and it will do everything for you.
Click to expand...
Click to collapse
Which script is that?
samabuelsamid said:
Which script is that?
Click to expand...
Click to collapse
My multitool in development section has stock restore included
holtenc said:
Have you tried re-doing all those instructions from the top with your bootloader unocked? instead of just trying to reflash motoboot?
I'm surprised it let your flash somethings while your bootloader was still locked.
Click to expand...
Click to collapse
bhp090808 said:
My multitool in development section has stock restore included
Click to expand...
Click to collapse
Downloading V4.1 now, thanks
bhp090808 said:
My multitool in development section has stock restore included
Click to expand...
Click to collapse
I flashed with the multitool and was able to get back where I started with the leaked PE lollipop version but something is still missing because I can't relock the bootloader.
I foolishly didn't create a backup. I know. Stupid of me.
I have a Moto G 2nd Gen model XT1064 (USA, purchased at Best Buy off contract, Single SIM). I can fastboot and I have TWRP recovery installed. I cannot find a rom that works however. Of all the .zips I've downloaded only one, a dual SIM UK version, boots. But it does not recognize my SIM or wifi chip. The others fail without giving me an error as to why.
UPDATE: This thread.... http://forum.xda-developers.com/moto-g-2014/general/restore-to-stock-t2873657 helped restore my wifi, though the firmware linked was a dual sim and I cannot enable my SIM card, the option is grayed out.
I have tried over the past day to try and get this to go back to its factory image with no luck at all. I have a Nexus 4, seeing as it has a toolkit and factory images readily available, its always easy to work on. This Moto G is a different story.
What do I need to get this back right? I may already have the files and not even realize it..
Thanks for any help!
canyoudig_it said:
I foolishly didn't create a backup. I know. Stupid of me.
I have a Moto G 2nd Gen model XT1064 (USA, purchased at Best Buy off contract, Single SIM). I can fastboot and I have TWRP recovery installed. I cannot find a rom that works however. Of all the .zips I've downloaded only one, a dual SIM UK version, boots. But it does not recognize my SIM or wifi chip. The others fail without giving me an error as to why.
UPDATE: This thread.... http://forum.xda-developers.com/moto-g-2014/general/restore-to-stock-t2873657 helped restore my wifi, though the firmware linked was a dual sim and I cannot enable my SIM card, the option is grayed out.
I have tried over the past day to try and get this to go back to its factory image with no luck at all. I have a Nexus 4, seeing as it has a toolkit and factory images readily available, its always easy to work on. This Moto G is a different story.
What do I need to get this back right? I may already have the files and not even realize it..
Thanks for any help!
Click to expand...
Click to collapse
Did you try the this one(Blur_Version.21.11.17.titan_retuaws.retuaws.en.US) from this site(http://sbf.droid-developers.org/phone.php?device=36)
edog11 said:
Did you try the this one(Blur_Version.21.11.17.titan_retuaws.retuaws.en.US) from this site
Click to expand...
Click to collapse
I have tried flashing it from TWRP. I get this error message...
Code:
Package expects build fingerprint of motorola/titan_retuaws/titan_umts:4.4.4/KXB21.85-17/23:user/release-keys or motorola/titan_retuaws/titan_umts:5.0/LXB22.39-6/5:user/release-keys; this device has motorola/titan-retaildsds/titan_umtsds:4.4.4/KXB21.85-14/9:user/release-keys.
E:Error executing updater binary in zip "/sdcard1/Blur_Version.21.11.17.titan_retuaws.retuaws.en.US.zip"
Error flashing zip "/sdcard1/Blur_Version.21.11.17.titan_retuaws.retuaws.en.US.zip"
Updating Partition details...
canyoudig_it said:
I have tried flashing it from TWRP. I get this error message...
Code:
Package expects build fingerprint of motorola/titan_retuaws/titan_umts:4.4.4/KXB21.85-17/23:user/release-keys or motorola/titan_retuaws/titan_umts:5.0/LXB22.39-6/5:user/release-keys; this device has motorola/titan-retaildsds/titan_umtsds:4.4.4/KXB21.85-14/9:user/release-keys.
E:Error executing updater binary in zip "/sdcard1/Blur_Version.21.11.17.titan_retuaws.retuaws.en.US.zip"
Error flashing zip "/sdcard1/Blur_Version.21.11.17.titan_retuaws.retuaws.en.US.zip"
Updating Partition details...
Click to expand...
Click to collapse
You cannot use custom recovery(TWRP) to flash this.
You need to follow this and you will lose data.
Unlock the bootloader.
Download Blur_Version.21.11.17.titan_retuaws.retuaws.en.US from droid-developers dot org slash phone device 36
Unzip that file into your fastboot folder
Enter Fastboot on your phone (how to: hold power and volume down until your device turns off, then hold it another 5-10 seconds, then let go and you should see a basic text screen)
Use these commands on your computer while being in the fastboot folder.
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 system system.img_sparsechunk.3
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
You should now be at stock Android 4.4.4 with an unlocked bootloader.
edog11 said:
You cannot use custom recovery(TWRP) to flash this.
You need to follow this and you will lose data.
Unlock the bootloader.
Download Blur_Version.21.11.17.titan_retuaws.retuaws.en.US from droid-developers dot org slash phone device 36
Unzip that file into your fastboot folder
Enter Fastboot on your phone (how to: hold power and volume down until your device turns off, then hold it another 5-10 seconds, then let go and you should see a basic text screen)
Use these commands on your computer while being in the fastboot folder.
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 system system.img_sparsechunk.3
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
You should now be at stock Android 4.4.4 with an unlocked bootloader.
Click to expand...
Click to collapse
THANK YOU! That did it! Everything works as it did before. You were a great help!
canyoudig_it said:
THANK YOU! That did it! Everything works as it did before. You were a great help!
Click to expand...
Click to collapse
Glad you were able to get you phone working again.
Warriors, come out and plaay.
EDIT: Found a link from another XDA thread... here's the direct download from Mega: https://mega.co.nz/#!mlIz0KCQ!lVXP5PCLRV9MRxwRdhEbKesEoq9UCPs4Lv8ec1Nx0ZY
edog11 said:
Did you try the this one(Blur_Version.21.11.17.titan_retuaws.retuaws.en.US) from this site(http://sbf.droid-developers.org/phone.php?device=36)
Click to expand...
Click to collapse
Anyone have another link/mirror? SBF Droid site is down.
While I did download it from another site, it seems a number of files are missing from the download. HEre's what I'm getting:
Kelleys-Mac-mini:Blur_Version.21.11.17.titan_retuaws.retuaws.en.US kelley$ ./fastboot flash motoboot motoboot.img
error: cannot load 'motoboot.img'
Kelleys-Mac-mini:Blur_Version.21.11.17.titan_retuaws.retuaws.en.US kelley$ cd /Users/kelley/Desktop/Blur_Version.21.11.17.titan_retuaws.retuaws.en.US\ 01-12-18-009
Kelleys-Mac-mini:Blur_Version.21.11.17.titan_retuaws.retuaws.en.US 01-12-18-009 kelley$ ./fastboot flash logo logo.bin
target reported max download size of 536870912 bytes
sending 'logo' (295 KB)...
OKAY [ 0.066s]
writing 'logo'...
OKAY [ 0.108s]
finished. total time: 0.174s
Kelleys-Mac-mini:Blur_Version.21.11.17.titan_retuaws.retuaws.en.US 01-12-18-009 kelley$ ./fastboot flash boot boot.img
error: cannot load 'boot.img'
Kelleys-Mac-mini:Blur_Version.21.11.17.titan_retuaws.retuaws.en.US 01-12-18-009 kelley$ ./fastboot flash recovery recovery.img
error: cannot load 'recovery.img'
Kelleys-Mac-mini:Blur_Version.21.11.17.titan_retuaws.retuaws.en.US 01-12-18-009 kelley$ ./fastboot flash recovery recovery.img
Click to expand...
Click to collapse
The SBF Droid website is down... and only gives an error message stating the following:
An error occurred.
Sorry, the page you are looking for is currently unavailable.
Please try again later.
If you are the system administrator of this resource then you should check the error log for details.
Faithfully yours, nginx.
Click to expand...
Click to collapse
My phone is unusable at this point; not bricked but might as well be as I can't make/receive phone calls nor texts. Can anyone PLEASE send me a valid link to a what's noted above? I accidentally flashed the wrong file to my phone and absolutely need to get it back to stock. THANK YOU... more than you'll EVER know!
thewinelover said:
While I did download it from another site, it seems a number of files are missing from the download. HEre's what I'm getting:
The SBF Droid website is down... and only gives an error message stating the following:
My phone is unusable at this point; not bricked but might as well be as I can't make/receive phone calls nor texts. Can anyone PLEASE send me a valid link to a what's noted above? I accidentally flashed the wrong file to my phone and absolutely need to get it back to stock. THANK YOU... more than you'll EVER know!
Click to expand...
Click to collapse
Sir..if you don't find a known good download soon..let me know, I can upload to my Drive..
Sent from my:
4.4.4_23.3.24 XT1080M
Droid Maxx Developer Edition
http://waynekent.com/page6.html
"Praise Jah" YOU people.!
Oh gosh that would be SO HELPFUL!!! Would you NWKENT? You might just save my phone!
PS - I'm a girl...
NWKENT said:
Sir..if you don't find a known good download soon..let me know, I can upload to my Drive..
Sent from my:
4.4.4_23.3.24 XT1080M
Droid Maxx Developer Edition
http://waynekent.com/page6.html
"Praise Jah" YOU people.!
Click to expand...
Click to collapse
thewinelover said:
Oh gosh that would be SO HELPFUL!!! Would you NWKENT? You might just save my phone!
PS - I'm a girl...
Click to expand...
Click to collapse
Here you go young lady....
RETUAWS_XT1064_4.4.4_KXB21.85-17_cid9_CFC.xml
Linky
EDIT: Here's the md5 checksum. ALWAYS verify these prior to installing.
b44ffe73058ebb8b85c853151f8c3e36
*RETUAWS_XT1064_4.4.4_KXB21.85-17_cid9_CFC.xml.zip
@fathergweedo, You sir, are the BOMB!! Thank you so much!!!!
thewinelover said:
@fathergweedo, You sir, are the BOMB!! Thank you so much!!!!
Click to expand...
Click to collapse
Once you get back to full stock 4.4.4, take a look at this so you won't need to do that again. This (TWRP) will also backup your PDS should you somehow bork the MEID or anything later...
Cheap insurance
EDIT: TWRP doesn't backup PDS by default. You must select it prior to the backup. Just thought I should clarify that.
fathergweedo said:
Once you get back to full stock 4.4.4, take a look at this so you won't need to do that again. This (TWRP) will also backup your PDS should you somehow bork the MEID or anything later...
Cheap insurance
Click to expand...
Click to collapse
And we're BAAAAAA-AAAAACK!!! With the right file, it's easy peasy, lemon squeezy!
You BETCHA! All of my apps are restoring now and as soon as they finish, that will be my next task!!! @fathergweedo, I cannot thank you enough. I'm thinking you're in the states, and if you are, you'll understand what I mean.... you brought new meaning to a HAPPY THANKSGIVING!!!! Cheers!!!
Thx!
fathergweedo said:
Once you get back to full stock 4.4.4, take a look at this so you won't need to do that again. This (TWRP) will also backup your PDS should you somehow bork the MEID or anything later...
Cheap insurance
Click to expand...
Click to collapse
THX so much! Had the same problem as the OP
fathergweedo said:
Here you go young lady....
RETUAWS_XT1064_4.4.4_KXB21.85-17_cid9_CFC.xml
Linky
EDIT: Here's the md5 checksum. ALWAYS verify these prior to installing.
b44ffe73058ebb8b85c853151f8c3e36
*RETUAWS_XT1064_4.4.4_KXB21.85-17_cid9_CFC.xml.zip
Click to expand...
Click to collapse
Thank you so much I spent the last 3 hours trying to recover from a softbrick and this did the trick. :good:
Bricked Moto X 2014? Fastboot flashing, ADB sideloading, nothing seems to work
Hello,
I have this Moto X 2nd gen (XT1092), and I wanted to install an Android Marshmallow OS last weekend.
I did it according to this article on XDA: http://forum.xda-developers.com/moto-x-2014/general/install-image-marshmallow-6-0-xt-1097-t3266858 , where an install image plus small install description is posted.
This is the first ‘non-standard’ thing I tried with this phone. It is not rooted, nor did I make any changes in the settings for developers, apart from enabling USB debugging. The device was running an stock version of Android 5.1, which I received the normal way(just an automatic system update).
Using some 'fastboot flash....' commands via the PC, the image should be installed. However, upon trying the first command: 'fastboot flash partition gpt.bin', the terminal responded with:
-------------------------
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.003s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.102s
-------------------------
Afterwards, my phone didnt boot to android anymore. The only thing it does is put me in "AP Fastboot Flash Mode (S)"
I have tried installing different stock Motorola images/zips for my phone, in order to try to get it back to how it was, but for every fastboot flash I want to do (except for the boot logo), I get the preflash validation error.
I also tried sideloading images via ADB via the recovery mode, bit this doesn’t work either:
When I try "adb sideload <IMAGE>.zip", it starts to send the file to the phone, and the phone receives it. Very quickly after completing the transfer, though, the phone can say two things (depending on what .zip file I try):
1.
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Package expects build fingerprint of motorola/victara_reteu/victara:5.0/LXE22.46-19.1/1:user/release-keys or motorola/victara_reteu/victara:5.1/LPE23.32-25.1/1:user/release-keys; this device has motorola/victara_reteu/victara:4.4.4/KXE21.187-42/41:user/re
Installation aborted.
2.
Finding update package...
Opening update package...
Verifying update package...
Installation aborted.
One thing to note is that when I try 'adb devices', it gives me:
-------------------------
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
TA99300SXJ sideload
-------------------------
It says that the device is in ADB sideload mode, which blocks me from using other ADB functions, like shell. Is there a way to get 'full' ADB acces?
I also tried using the official Motorola “RDS Lite” software, as some people say this can be used to correctly flash an image to the phone, but this program just does not see my phone.
I did install all drivers, and Windows recognizes the device correctly, in both fastboot and ADB (recovery) mode.
Another thing I wanted to do to solve this, is to unlock the bootloader, as some people on forums said that this would help. However, when I try “fastboot oem unlock UNIQUEKEY” with the key I got from the Motorola website, the bootloader responds with the message stating that I have to enable unlocking the bootloader via developer settings. And obviously, I cannot go to settings to enable this.
-------------------------
I’m very stuck here, and I would be the intensely happy if there would be someone around who can help me get my phone back to life!
I do have experience with flashing Android ROMs/Images/Zips, but not on Motorola devices.
I reckon that this:
“Package expects build fingerprint of motorola/victara_reteu/victara:5.0/LXE22.46-19.1/1:user/release-keys or motorola/victara_reteu/victara:5.1/LPE23.32-25.1/1:user/release-keys; this device has motorola/victara_reteu/victara:4.4.4/KXE21.187-42/41:user/re”
could possibly be caused by an incorrect zip file. If that is the case, is there any way to obtain the proper file?
I did read about some special micro USB cables connecting the normally unused pin 4. Could this be helpful?
Any help would be IMMENSELY appreciated. I'm not ready to give up the fight!
Kind regards,
Ostheer
This same thing happened to me today. Ive had my fair share of rooted phone issues but this one is a mystery to me. Ive rooted every other Moto device [G, G '14, X, X Pure] And now a new issue arises.
I used a .bat file from CLARK_RETUS_5.1.1_LPH23.116-18_cid9_subsidy-DEFAULT_CFC.xml_SHAWN5162 . It finished and booted into bootloader but wont go anywhere from there. I have a feeling Ive reset to a locked state with no boot file.
Device is LOCKED. Status Code:0
Software status: Modified
$ Normal Powerup
failed to validate boot img
boot up failed
fastboot oem get_unlock_data
(bootloader) could not get unlock data
boot flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.016s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.040s
Just like you I tried several fixes and no luck.
1. ADB Lite: Same issue
2. mfastboot Same issue
3. RSD Lite: Does not recognize my devices (win 10 / sdk / all drivers / redownloaded 3 times)
4. any bat file I try / manual code / or adb all fail
There must be a solution to this. I want Marshmallow 6.0 just as much as the next guy to work on my phone. Thanks for the help
WhiteRaven96 said:
This same thing happened to me today. Ive had my fair share of rooted phone issues but this one is a mystery to me. Ive rooted every other Moto device [G, G '14, X, X Pure] And now a new issue arises.
I used a .bat file from CLARK_RETUS_5.1.1_LPH23.116-18_cid9_subsidy-DEFAULT_CFC.xml_SHAWN5162 . It finished and booted into bootloader but wont go anywhere from there. I have a feeling Ive reset to a locked state with no boot file.
Device is LOCKED. Status Code:0
Software status: Modified
$ Normal Powerup
failed to validate boot img
boot up failed
fastboot oem get_unlock_data
(bootloader) could not get unlock data
..... ..... .....
There must be a solution to this. I want Marshmallow 6.0 just as much as the next guy to work on my phone. Thanks for the help
Click to expand...
Click to collapse
At this point I would be happy to get anything to work on it, 6.0 is not a requirement for me anymore.
For me it says: "Software status: Official", and getting the unlock data works. Still can't unlock though, as this should've been enabled in settings apparently.
ostheer said:
At this point I would be happy to get anything to work on it, 6.0 is not a requirement for me anymore.
For me it says: "Software status: Official", and getting the unlock data works. Still can't unlock though, as this should've been enabled in settings apparently.
Click to expand...
Click to collapse
Well there is your problem, your bootloader is locked. You can't flash firmware that is not for your model/carrier with a locked bootloader. It absolutely will fail.
Try flashing this with mfastboot:
http://www.filefactory.com/file/i8htlx8fqpv/VICTARA_RETEU_XT1092_5.1_LPE23.32-25.3_cid7_CFC.xml.zip
Most likely gpt.bin and motoboot will fail to flash, just keep flashing all the files even if those 2 fail.
If this works, do NOT use the OTA update to get to 6.0 there is a high probability that you will hard brick your phone if you use OTA, and there is no way to fix that currently.
Because of what you did, you will have to wait for a full 6.0 firmware for the xt1092EU. Do not flash anything else until that is released.
Sent from my XT1095 using Tapatalk
AGISCI said:
Well there is your problem, your bootloader is locked. You can't flash firmware that is not for your model/carrier with a locked bootloader. It absolutely will fail.
Try flashing this with mfastboot:
http://www.filefactory.com/file/i8htlx8fqpv/VICTARA_RETEU_XT1092_5.1_LPE23.32-25.3_cid7_CFC.xml.zip
Most likely gpt.bin and motoboot will fail to flash, just keep flashing all the files even if those 2 fail.
If this works, do NOT use the OTA update to get to 6.0 there is a high probability that you will hard brick your phone if you use OTA, and there is no way to fix that currently.
Because of what you did, you will have to wait for a full 6.0 firmware for the xt1092EU. Do not flash anything else until that is released.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
@AGISCI,
Thank you for your reply. I am currently downloading the file you linked, and will try to flash it using mfastboot as soon as it finishes downloading.
I did indeed hear that using the OTA afterwards is not something you will want to do.
ostheer said:
At this point I would be happy to get anything to work on it, 6.0 is not a requirement for me anymore.
For me it says: "Software status: Official", and getting the unlock data works. Still can't unlock though, as this should've been enabled in settings apparently.
Click to expand...
Click to collapse
http://forum.xda-developers.com/mot...-0-xt-1097-t3266858/post64274827#post64274827 POST #33
This I think is your delay. I just woke up today and noticed my phone now says UNLOCKED I didnt do anything else but attempt all my failed steps on another computer and a reboot [which had not been done since system failure. So it boot up like it was unlocked and didnt go further. Back to bootloader mode, let see if it works
YES! Got it to load up and boot using this 6.0 zip http://forum.xda-developers.com/moto-x-2014/development/rom-installation-rsd-t3263800
However now my SIM card isnt being recognized. Which ssems to happen all the time when using a file from another country. Isnt there a simple solution for this fix?
WhiteRaven96 said:
http://forum.xda-developers.com/mot...-0-xt-1097-t3266858/post64274827#post64274827 POST #33
This I think is your delay. I just woke up today and noticed my phone now says UNLOCKED I didnt do anything else but attempt all my failed steps on another computer and a reboot [which had not been done since system failure. So it boot up like it was unlocked and didnt go further. Back to bootloader mode, let see if it works
YES! Got it to load up and boot using this 6.0 zip http://forum.xda-developers.com/moto-x-2014/development/rom-installation-rsd-t3263800
However now my SIM card isnt being recognized. Which ssems to happen all the time when using a file from another country. Isnt there a simple solution for this fix?
Click to expand...
Click to collapse
That is great news! I am still downloading the zip AGISCI linked.
So if I'm correct, in the fastboot screen it now says "device is unlocked" for you?
What steps did you make to try to unlock the bootloader?
Also, am I correct to assume that you used fastboot/mfastboot to flash your zip in the end?
How is it possible? Your bootloader just got unlocked without root!
I will be more than happy if you explain again what you did and what happend exactly.
Thanks.
Whenever you flash a firmware meant for another region/carrier, you are also flashing the modem/radio that supports that region/carrier, so you have to find the firmware that supports your device/region/carrier and flash the modem/radio from it, in bootloader mode:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
These are the files you need to flash "NON-HLOS.bin" and "fsg.mbn"
AGISCI said:
Well there is your problem, your bootloader is locked. You can't flash firmware that is not for your model/carrier with a locked bootloader. It absolutely will fail.
Try flashing this with mfastboot:
http://www.filefactory.com/file/i8htlx8fqpv/VICTARA_RETEU_XT1092_5.1_LPE23.32-25.3_cid7_CFC.xml.zip
Most likely gpt.bin and motoboot will fail to flash, just keep flashing all the files even if those 2 fail.
If this works, do NOT use the OTA update to get to 6.0 there is a high probability that you will hard brick your phone if you use OTA, and there is no way to fix that currently.
Because of what you did, you will have to wait for a full 6.0 firmware for the xt1092EU. Do not flash anything else until that is released.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
The download completed, and I have tried flashing it using mfastboot:
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot reboot-bootloader
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 system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot flash system system.img_sparsechunk.6
mfastboot flash system system.img_sparsechunk.7
mfastboot flash modem NON-HLOS.bin
mfastboot flash fsg fsg.mbn
what I get is the following:
the gpt.bin and motoboot.img indeed failed, logo.bin, boot.img, recovery.img, NON-HLOS.bin and fsg.mbn succeeded.
the system.img_sparsechunk.X files give this:
-------------------------
C:\Program Files (x86)\Minimal ADB and Fastboot\VICTARA_RETEU_XT1092_5.1_LPE23.3
2-25.3_cid7_CFC.xml>mfastboot flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (256681 KB)...
OKAY [ 8.068s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.181s
-------------------------
while the phone responds with:
-------------------------
cmd: getvar:max-sparse-size
cmd: download:0faaa7a0
cmd: flash:system
version downgraded for system
Invalid PIV signed system image
-------------------------
Any ideas? This zip seemed to have done 'better' than other, but the phone still doesn't accept it.
ostheer said:
The download completed, and I have tried flashing it using mfastboot:
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot reboot-bootloader
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 system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot flash system system.img_sparsechunk.6
mfastboot flash system system.img_sparsechunk.7
mfastboot flash modem NON-HLOS.bin
mfastboot flash fsg fsg.mbn
what I get is the following:
the gpt.bin and motoboot.img indeed failed, logo.bin, boot.img, recovery.img, NON-HLOS.bin and fsg.mbn succeeded.
the system.img_sparsechunk.X files give this:
-------------------------
C:\Program Files (x86)\Minimal ADB and Fastboot\VICTARA_RETEU_XT1092_5.1_LPE23.3
2-25.3_cid7_CFC.xml>mfastboot flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (256681 KB)...
OKAY [ 8.068s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.181s
-------------------------
while the phone responds with:
-------------------------
cmd: getvar:max-sparse-size
cmd: download:0faaa7a0
cmd: flash:system
version downgraded for system
Invalid PIV signed system image
-------------------------
Any ideas? This zip seemed to have done 'better' than other, but the phone still doesn't accept it.
Click to expand...
Click to collapse
It sounds like the download of the .zip is corrupt. You will need to download the zip again. There is a list of md5 values in an xml file inside the zip. If the md5 is different it won't flash as a safety precaution.
Sent from my XT1095 using Tapatalk
ostheer said:
That is great news! I am still downloading the zip AGISCI linked.
So if I'm correct, in the fastboot screen it now says "device is unlocked" for you?
What steps did you make to try to unlock the bootloader?
Also, am I correct to assume that you used fastboot/mfastboot to flash your zip in the end?
Click to expand...
Click to collapse
You are indeed correct. I dont think using another computer helped, although I managed to get FLASH Partition gpt.bin to work first try. What I think happened was my friend [not knowing it was in bootloader] did the bootloader button sequence and failed so instead it just tried to boot up [Stopped @ unlocked bootloader screen]
SO after I got 6.0 to work the radio network wasnt the same so now my SIM isnt being recognized.
So I looked for a simple solution and found directions
The Radio uses these lines of the flash process:
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
I searched for Moto X radio files but no luck, however I did find this link for Moto G which is everything I need to find the solution myself with instructions
http://forum.xda-developers.com/showthread.php?t=2649763
:highfive:
---------- Post added at 08:46 PM ---------- Previous post was at 08:27 PM ----------
OrenGazala said:
How is it possible? Your bootloader just got unlocked without root!
I will be more than happy if you explain again what you did and what happend exactly.
Thanks.
Click to expand...
Click to collapse
I believe that Root is a step that comes after bootloader
[YOUR PHONE]
1. unlock-Bootloader --> mfastboot oem get_unlock_data
This is the first step Motorola tells you to do. Go Here: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
2. Install TWRP --> mfastboot flash recovery 'your twrp.img'
At this point your phone should turn on, if not your not finished
3. Install Root --> push SuperSU-v2.--
This zip I have CLARK_RETUS_5.1.1_LPH23.116-18_cid9_subsidy-DEFAULT_CFC.xml_SHAWN5162.zip started this whole mess but it was made to where you can relock your phone after returning it to stock. Problem was that when I ran the .bat file it never took the files so it dumped every partition THEN locked me out, or just pretended to, Im still unsure because I think all I did was try to push a flash line by line [eg. gpt.bin,motoboot,logo...] only got to motoboot and then did a reset. :highfive:
bootloader unlock question
AGISCI said:
It sounds like the download of the .zip is corrupt. You will need to download the zip again. There is a list of md5 values in an xml file inside the zip. If the md5 is different it won't flash as a safety precaution.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
Thanks for the reply. I checked all MD5's and compared them to the ones I generated with a MD5 checksum tool, they all match. I am downloading the zip again, but theoretically that shouldn't help as de MD5's are good.
"Invalid signed image" stays the problem here, unfortunately...
Is there no way to unlock the bootloader if you didn't enable this via settings in Android?
ostheer said:
Thanks for the reply. I checked all MD5's and compared them to the ones I generated with a MD5 checksum tool, they all match. I am downloading the zip again, but theoretically that shouldn't help as de MD5's are good.
"Invalid signed image" stays the problem here, unfortunately...
Is there no way to unlock the bootloader if you didn't enable this via settings in Android?
Click to expand...
Click to collapse
No there is no way to unlock it if you didn't.
Question what version of android were you on before you did this? 5.1? With stagefright patch?
Sent from my XT1095 using Tapatalk
AGISCI said:
No there is no way to unlock it if you didn't.
Question what version of android were you on before you did this? 5.1? With stagefright patch?
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
Thought so,
I was on an official 5.1 build, presumably with the patch indeed, as my phone was fully updated and the patch came out in September. For the patch I can't be 100% sure though.
I downloaded the zip for the second time, but as expected after the MD5 check, the results were the same...
ostheer said:
Thought so,
I was on an official 5.1 build, presumably with the patch indeed, as my phone was fully updated and the patch came out in September. For the patch I can't be 100% sure though.
I downloaded the zip for the second time, but as expected after the MD5 check, the results were the same...
Click to expand...
Click to collapse
I don't know if this is the reason, but maybe if you did not have the stagefright patch you need the firmware without it. Here is the 5.1 without stagefright to try:
http://www.filefactory.com/file/w34zg9w3v4h/VICTARA_RETEU_XT1092_5.1_LPE23.32-25.1_cid7_CFC.xml.zip
Sent from my XT1095 using Tapatalk
AGISCI said:
I don't know if this is the reason, but maybe if you did not have the stagefright patch you need the firmware without it. Here is the 5.1 without stagefright to try:
http://www.filefactory.com/file/w34zg9w3v4h/VICTARA_RETEU_XT1092_5.1_LPE23.32-25.1_cid7_CFC.xml.zip
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
I am currently downloading this zip, and also some others.
Curiosity:
How is the phone actually checking the file signatures? What is it comparing them to?
I'm wondering how did I manage to make the phone unable to boot, while the bootloader doesn't allow anything to be flashed?
ostheer said:
I am currently downloading this zip, and also some others.
Curiosity:
How is the phone actually checking the file signatures? What is it comparing them to?
I'm wondering how did I manage to make the phone unable to boot, while the bootloader doesn't allow anything to be flashed?
Click to expand...
Click to collapse
The images are also signed by motorola with a special key that only they have and know. If the key does not match with your installed firmware flashing will fail.
Sent from my XT1095 using Tapatalk
AGISCI said:
I don't know if this is the reason, but maybe if you did not have the stagefright patch you need the firmware without it. Here is the 5.1 without stagefright to try:
http://www.filefactory.com/file/w34zg9w3v4h/VICTARA_RETEU_XT1092_5.1_LPE23.32-25.1_cid7_CFC.xml.zip
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
I downloaded the zip without stagefright, and flashing it using the described procedure again gave the error 'Preflash validation failed' - 'Invalid PIV signed system image'.
Strangely though, flashing motoboot.img actually did work for the first time. (!)
Also flashing the recovery.img works for most zips I tried. That's rather strange as apparently they are being checked too: flashing a twrp recovery (unsurprisingly) didn't work: "mismatched partition size (recovery)".
AGISCI said:
The images are also signed by motorola with a special key that only they have and know. If the key does not match with your installed firmware flashing will fail.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
I requested a compatible stock zip from Motorola for my device, using a ticket on their site. Probably they won't be very eager to supply it though.