Related
First: I'm not blaming anyone associated with the sunshine unlock method. This is definitely my fault.
I unlocked rooted my phone and stayed on 4.4.2 and just today I used the sunshine app to unlock my boot loader. I then flashed twrp recovery using the twrp app in the play store. Then I did a backup and then I tried to update the kernel and radio using this utility http://forum.xda-developers.com/moto-x/development/rom-stock-rooted-vzw-212-55-26-t2829123
It said that it worked but when I tried to boot up again it started a boot loop.
I tried manually flashing the 4.2.2 kernels again but that didn't work. Tried manually flashing the 4.4.4 ROM, didn't work. Tried flashing the 4.2.2 ROM, didn't work. Tried flashing 4.2.2 with rsd and it failed.
Now it's stuck in fastboot and won't boot into recovery or even try to boot, even if I try rebooting with adb.
I would love to keep root, but if I have to I'll do the root again if possible.
**EDIT**
If you have done the same bone-head move I made, then follow these simple steps.
1. Use RSD lite to update to 4.4.4
2. Follow this guide to then root your device once you have updated to 4.4.4
This works because your bootloader is unlocked, thanks to sunshine.
wisenick said:
First: I'm not blaming anyone associated with the sunshine unlock method. This is definitely my fault.
I unlocked rooted my phone and stayed on 4.4.2 and just today I used the sunshine app to unlock my boot loader. I then flashed twrp recovery using the twrp app in the play store. Then I did a backup and then I tried to update the kernel and radio using this utility http://forum.xda-developers.com/moto-x/development/rom-stock-rooted-vzw-212-55-26-t2829123
It said that it worked but when I tried to boot up again it started a boot loop.
I tried manually flashing the 4.2.2 kernels again but that didn't work. Tried manually flashing the 4.4.4 ROM, didn't work. Tried flashing the 4.2.2 ROM, didn't work. Tried flashing 4.2.2 with rsd and it failed.
Now it's stuck in fastboot and won't boot into recovery or even try to boot, even if I try rebooting with adb.
I would love to keep root, but if I have to I'll do the root again if possible.
Click to expand...
Click to collapse
You should have never attempted to downgrade...
Try using fastboot & mfastboot.
Unplug, then turn off the phone. Boot it into bootloader mode. Once in BL, plug usb into PC.
You must have at least minimal adb/fastboot, AND the mfastboot binary (search it).
Unzip the 4.4.4 SBF into the SAME FOLDER that both fastboot and mfastboot are in.
Open a command prompt, browse to the folder containing the unzipped files, fastboot, and mfastboot. Now execute the following commands in this exact order:
fastboot flash bootloader motoboot.img
fastboot flash partition gpt.bin
fastboot reboot-bootloader
[the device will reboot into the bootloader] ignore the fact that some commands are being run twice...
fastboot flash bootloader motoboot.img
fastboot flash partition gpt.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
mfastboot flash system system.img [make absolutely sure to use the Mfastboot binary for flashing system.img]
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 reboot
If you see an error about variable not supported, ignore it. If you get a different error, post back with a screenshot.
Does it boot into android now? You should be 100% stock, unlocked. Ready to flash TWRP and root.
wisenick said:
First: I'm not blaming anyone associated with the sunshine unlock method. This is definitely my fault.
I unlocked rooted my phone and stayed on 4.4.2 and just today I used the sunshine app to unlock my boot loader. I then flashed twrp recovery using the twrp app in the play store. Then I did a backup and then I tried to update the kernel and radio using this utility http://forum.xda-developers.com/moto-x/development/rom-stock-rooted-vzw-212-55-26-t2829123
It said that it worked but when I tried to boot up again it started a boot loop.
I tried manually flashing the 4.2.2 kernels again but that didn't work. Tried manually flashing the 4.4.4 ROM, didn't work. Tried flashing the 4.2.2 ROM, didn't work. Tried flashing 4.2.2 with rsd and it failed.
Now it's stuck in fastboot and won't boot into recovery or even try to boot, even if I try rebooting with adb.
I would love to keep root, but if I have to I'll do the root again if possible.
Click to expand...
Click to collapse
RSD 422 means a downgrade. What did it "say"?
Downgrading is the no no.
---------- Post added at 06:11 PM ---------- Previous post was at 06:07 PM ----------
http://forum.xda-developers.com/showpost.php?p=55491148&postcount=10
samwathegreat said:
You should have never attempted to downgrade...
Try using fastboot & mfastboot.
Unplug, then turn off the phone. Boot it into bootloader mode. Once in BL, plug usb into PC.
You must have at least minimal adb/fastboot, AND the mfastboot binary (search it).
Unzip the 4.4.4 SBF into the SAME FOLDER that both fastboot and mfastboot are in.
Open a command prompt, browse to the folder containing the unzipped files, fastboot, and mfastboot. Now execute the following commands in this exact order:
fastboot flash bootloader motoboot.img
fastboot flash partition gpt.bin
fastboot reboot-bootloader
[the device will reboot into the bootloader] ignore the fact that some commands are being run twice...
fastboot flash bootloader motoboot.img
fastboot flash partition gpt.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
mfastboot flash system system.img [make absolutely sure to use the Mfastboot binary for flashing system.img]
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 reboot
If you see an error about variable not supported, ignore it. If you get a different error, post back with a screenshot.
Does it boot into android now? You should be 100% stock, unlocked. Ready to flash TWRP and root.
Click to expand...
Click to collapse
Thank you, however when I try the first command "fastboot flash boot loader moto boot.img" it says "(bootloader) Variable not supported! Then says (bootloader) Permission denied
But I followed the rest of the directions and it still will only boot into fastboot.
wisenick said:
Thank you, however when I try the first command "fastboot flash boot loader moto boot.img" it says "(bootloader) Variable not supported! Then says (bootloader) Permission denied
Click to expand...
Click to collapse
Did you really put spaces in between boot and loader? And Moto and boot?
samwathegreat said:
Did you really put spaces in between boot and loader? And Moto and boot?
Click to expand...
Click to collapse
No sorry, auto correct on the wife's phone.
wisenick said:
No sorry, auto correct on the wife's phone.
Click to expand...
Click to collapse
A "Permission denied" error sounds strange to me....don't recall having seen that one before.
Though I'm rather certain that your downgrade attempt (big no-no) is the culprit, I'm curious if @jcase might have any suggestions...
1) I don't think you are bricked, this should be fixable. This is due to you flashing older firmware to a device that has been updated, nothing to do with sunshine.
2) your title makes it sound like sunshine to blame, this is really bad for me. SunShine CANT brick motorola (nor htc) phones. We simply have too many safety checks, and verification. If you were able to flash and boot TWRP (which you were because you took a backup) then it can't be sunshine. It would be great if you changed the title to be more accurate.
Having said that, I have no problem helping you recover your phone, it certainly isn't bricked
I'm out from 10amPST to 2pmPST tomorrow, but please email me jcase AT cunninglogic DOT com, and I will have you up on your feet in minutes. Probably setup teamviewer and I will just remote in and do my best.
wisenick said:
First: I'm not blaming anyone associated with the sunshine unlock method. This is definitely my fault.
I unlocked rooted my phone and stayed on 4.4.2 and just today I used the sunshine app to unlock my boot loader. I then flashed twrp recovery using the twrp app in the play store. Then I did a backup and then I tried to update the kernel and radio using this utility http://forum.xda-developers.com/moto-x/development/rom-stock-rooted-vzw-212-55-26-t2829123
It said that it worked but when I tried to boot up again it started a boot loop.
I tried manually flashing the 4.2.2 kernels again but that didn't work. Tried manually flashing the 4.4.4 ROM, didn't work. Tried flashing the 4.2.2 ROM, didn't work. Tried flashing 4.2.2 with rsd and it failed.
Now it's stuck in fastboot and won't boot into recovery or even try to boot, even if I try rebooting with adb.
I would love to keep root, but if I have to I'll do the root again if possible.
Click to expand...
Click to collapse
samwathegreat said:
Now execute the following commands in this exact order:
fastboot flash bootloader motoboot.img
fastboot flash partition gpt.bin
Click to expand...
Click to collapse
I don't have the sbf files handy right now, so I can't check -- are you sure the order is bootloader then gpt? I thought it was the other way around. A quick check of the xml file in the sbf will give the correct order.
jcase said:
...nothing to do with sunshine.
2) your title makes it sound like sunshine to blame...
Click to expand...
Click to collapse
That is what I first thought when I read the subject...
@wisenick, you even mention in your OP you don't blame Sunshine, so why mention it in the subject?
Can you change the subject of this thread to "Attempted to Downgrade and now bricked" or "Attempted to downgrade and now phone wont boot"? That would be more accurate.
piccit said:
I don't have the sbf files handy right now, so I can't check -- are you sure the order is bootloader then gpt? I thought it was the other way around. A quick check of the xml file in the sbf will give the correct order.
Click to expand...
Click to collapse
Just checked the XML and it is gpt then bootloader. I'll see if that fixes things.
Try flashing an alternate bootloader like TWRP or CWN with mfastboot. My recovery wasn't working for awhile and all I had to do was reflash it.
Verttex said:
Try flashing an alternate bootloader like TWRP or CWN with mfastboot. My recovery wasn't working for awhile and all I had to do was reflash it.
Click to expand...
Click to collapse
Thank you but I've tried that. It says that it flashed but when I try to boot into recovery it simply boots into fastboot
piccit said:
I don't have the sbf files handy right now, so I can't check -- are you sure the order is bootloader then gpt? I thought it was the other way around. A quick check of the xml file in the sbf will give the correct order.
Click to expand...
Click to collapse
Double checked the order and according to the xml , its gpt first. However I still get an error when I try to flash motoboot
Well I couldn't handle not having a phone much longer so I used rsd to go to 4.4.4, have I lost root?
wisenick said:
Well I couldn't handle not having a phone much longer so I used rsd to go to 4.4.4, have I lost root?
Click to expand...
Click to collapse
If Sunshine unlocked your bootloader, you should be able to do whatever.
wisenick said:
Well I couldn't handle not having a phone much longer so I used rsd to go to 4.4.4, have I lost root?
Click to expand...
Click to collapse
Yes you lost root! but
If you used sunshine, you turned your consumer phone into a developer phone, meaning you will always be able to root it trivially and properly.
True. if your back in android w/o root
Download Supersu in a zip file
boot to bootloader
fastboot flash new recovery
reboot into the new recovery
flash supersu zip
you have root! Easy w/ an unlocked bootloader!
Hello everybody. I'm having some problems flashing TWRP after unlocking the bootloader.
First of all, after unlocking the BL, I have flashed back the stock logo using
Code:
fastboot flash logo logo.bin
Then I tried flashing TWRP.
Code:
fastboot flash recovery recovery.img
Everything is successful, but booting to recovery from bootloader turns the phone off, and using
Code:
adb reboot recovery
brings about a 'dead android' screen with 'No command' written below it. I had to force reboot.
The phone itself works fine, and I was able to boot to TWRP, using the same .img file,
Code:
fastboot boot recovery.img
, and flash SU and whatever.
I don't really have a clue about what's going on here, can anybody point me in the right direction?
Thanks in advance
Nevermind, solved using TWRP manager app, and flashing the recovery from Android. Still don't know why I wasn't able to flash recovery from fastboot.
totalnoob34 said:
Nevermind, solved using TWRP manager app, and flashing the recovery from Android. Still don't know why I wasn't able to flash recovery from fastboot.
Click to expand...
Click to collapse
I think you should use mfastboot instead of fastboot
Sent from my XT1068 using XDA Free mobile app
ggunzio said:
I think you should use mfastboot instead of fastboot
Sent from my XT1068 using XDA Free mobile app
Click to expand...
Click to collapse
Mfastboot? I am using Linux, I think that it's for Windows only. Anyway, I don't think the problem is on computer side, since the commands were successful both on the pc and the phone.
ggunzio said:
I think you should use mfastboot instead of fastboot
Sent from my XT1068 using XDA Free mobile app
Click to expand...
Click to collapse
I used fastboot for the same thing and it worked flawlessly.
Hello need help tracking down stock turbo firmware. The Motofirmware website (http://motofirmware.center/files/category/23-droid-turbo/downloads) are corrupted. The links in this thread are all dead: http://forum.xda-developers.com/moto-maxx/general/quark-stock-firmware-moto-maxx-droid-t3063470. Does anyone know of another source for stock 5.1?
http://motofirmware.center/
Stanleywinthrop said:
Hello need help tracking down stock turbo firmware. Does anyone know of another source for stock 5.1?
Click to expand...
Click to collapse
Here is the file download link for the latest xt1254 droid turbo 5.1 lollipop firmware:
https://www.androidfilehost.com/?fid=24052804347843637
Thanks, jala, but if you had bothered to fully read you'd see that the files on that website are corrupted.
jalal-jap said:
http://motofirmware.center/
Click to expand...
Click to collapse
Thanks, classic, i'll give this a try.
classic757 said:
Here is the file download link for the latest xt1254 droid turbo 5.1 lollipop firmware:
https://www.androidfilehost.com/?fid=24052804347843637
Click to expand...
Click to collapse
Stanleywinthrop said:
Thanks, classic, i'll give this a try.
Click to expand...
Click to collapse
No problem. Please let me know how it turns out.
Stanleywinthrop said:
Thanks, jala, but if you had bothered to fully read you'd see that the files on that website are corrupted.
Click to expand...
Click to collapse
i have same problem. extract it whit "7ZIP" and no corrupted for me.
http://www.rootjunkysdl.com/getdown...o/Firmware/VRZ_XT1254_SU4TL-44_44_CFC.xml.zip -> Full firmware (not OTA) of the most recent version of 5.1
TheSt33v said:
http://www.rootjunkysdl.com/getdown...o/Firmware/VRZ_XT1254_SU4TL-44_44_CFC.xml.zip -> Full firmware (not OTA) of the most recent version of 5.1
Click to expand...
Click to collapse
I get this error:
http://i.imgur.com/EOPsxnB.png
dmginc said:
I get this error:
http://i.imgur.com/EOPsxnB.png
Click to expand...
Click to collapse
Are you using RSDlite? If so, you're getting this error (I think) because the PRODUCT_CONFIGURATION.xml file has instructions for other phone models besides the Turbo in it. If I remember correctly, I got around this by deleting the info for everything not labeled QUARK_VERIZON in this file. However, since RSDlite basically just automates fastboot, a better option is to use fastboot to flash this firmware, in my opinion.
If you decide to flash the firmware this way, place all of the files from the full firmware into the directory that you installed fastboot, and enter the following commands after your phone is plugged into your computer in bootloader mode:
fastboot flash partition gpt.bin
fastboot flash motoboot bootloader.img
fastboot flash radio radio.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk1
fastboot flash system system.img_sparsechunk2
fastboot flash system system.img_sparsechunk3
<repeat until all sparsechunks are flashed>
fastboot erase ddr
fastboot erase cache
fastboot erase userdata (NOTE: this command effectively performs a factory reset, and will erase all of your data)
Then boot, and you will have done everything that RSDlite would have done.
Oh thanks. Good info. Is there a write up on using fastboot anywhere? These forums are pretty poorly maintained and no good stickies anywhere
Edit: Oh, you edited your post. Awesome. Thanks.
The root junky fxz is that for rsd lite when I look at the contents the system image is in several sections and says system.img sparsechunk and has 10 sections. I have never seen this in an fxz. Is this a new way of flashing the system image.
TheSt33v said:
Are you using RSDlite? If so, you're getting this error (I think) because the PRODUCT_CONFIGURATION.xml file has instructions for other phone models besides the Turbo in it. If I remember correctly, I got around this by deleting the info for everything not labeled QUARK_VERIZON in this file. However, since RSDlite basically just automates fastboot, a better option is to use fastboot to flash this firmware, in my opinion.
If you decide to flash the firmware this way, place all of the files from the full firmware into the directory that you installed fastboot, and enter the following commands after your phone is plugged into your computer in bootloader mode:
fastboot flash partition gpt.bin
fastboot flash motoboot bootloader.img
fastboot flash radio radio.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk1
fastboot flash system system.img_sparsechunk2
fastboot flash system system.img_sparsechunk3
<repeat until all sparsechunks are flashed>
fastboot erase ddr
fastboot erase cache
fastboot erase userdata (NOTE: this command effectively performs a factory reset, and will erase all of your data)
Then boot, and you will have done everything that RSDlite would have done.
Click to expand...
Click to collapse
Is it possible for me to relock my bootloader using adb fastboot? I don't want to do it accidentally while messing around with different roms and wiping my way back to stock.
When in fastboot, type "fastboot oem lock" (without the quotations"
Btrusa said:
When in fastboot, type "fastboot oem lock" (without the quotations"
Click to expand...
Click to collapse
Wouldn't that lock the bootloader?
Is it even possible to re-lock?
From what I understand he wants to avoid locking the bootloader...
Edit: nevermind I looked it up... Should have just done that the first time... ("I have seen quite of few people screw up their devices by not knowing what they are doing. So I am making this thread to simply tell people not familiar with fastboot what they should and should not do.
Fastboot oem unlock will unlock your bootloader and do a complete wipe of your device. As far as I know the only way for something to go wrong here is if you're device is low on battery and shuts off during the process. Either plug it in or have a "good" amount of juice left in your battery. To be 100 percent sure plug it in.
Before I get into oem lock IMHO you should only use this command for one thing only. Getting the device ready to send into motorola for the LGT upgrade or a another warranty repair or some sort. When done properly it is completely safe but there is no reason to do to go back to "stock".
Fastboot oem lock. Do not issue this command unless you are absolutely sure you have the correct software on your device. The correct software is what you get from the motodev site for your device. You need the official sofware images for your specific device AND REGION. If it is not released then DO NOT re-lock the device. If you have a OTA installed you will need to flash back to the motodev images first.")
dmginc said:
Is it possible for me to relock my bootloader using adb fastboot? I don't want to do it accidentally while messing around with different roms and wiping my way back to stock.
Click to expand...
Click to collapse
Nope
So is the fastboot flash motoboot bootloader.img just the Motorola "M" splash screen?
Sent from my XT1254 using Tapatalk
dmginc said:
So is the fastboot flash motoboot bootloader.img just the Motorola "M" splash screen?
Click to expand...
Click to collapse
No, that is the actual bootloader. The code that manages device startup, takes fastboot commands, and prohibits unsigned images from booting (when locked).
The splash screen is flashed with:
fastboot flash logo logo.bin
unhappybirthday said:
No, that is the actual bootloader. The code that manages device startup, takes fastboot commands, and prohibits unsigned images from booting (when locked).
The splash screen is flashed with:
fastboot flash logo logo.bin
Click to expand...
Click to collapse
So, back to my original question. When flashing back to stock with adb, but wanting to keep my bootloader unlocked, what should I do?
dmginc said:
So, back to my original question. When flashing back to stock with adb, but wanting to keep my bootloader unlocked, what should I do?
Click to expand...
Click to collapse
I can only speak from my experience. I was on the KitKat bootloader and used mofo to flash lollipop. I unlocked with sunshine and installed twrp. Then I flashed the lollipop bootloader with the fastboot command . Still unlocked.
Sent from my DROID Turbo using Tapatalk.
Hey There, i just got Motorola Moto x (2nd Gen) and it's currently running android 4.4.4 and is AT&T variant. Can any one tell me how can i update it to Marshmallow with/without international variant ?
Update process from PC will be preferred.
abdullah.ahsan11 said:
Hey There, i just got Motorola Moto x (2nd Gen) and it's currently running android 4.4.4 and is AT&T variant. Can any one tell me how can i update it to Marshmallow with/without international variant ?
Update process from PC will be preferred.
Click to expand...
Click to collapse
As its att and bootloader is locked so you cant go further.. Wait for officially update.. Well why you are on kitkat still? You should get lolipop by now..
Salik Iqbal said:
As its att and bootloader is locked so you cant go further.. Wait for officially update.. Well why you are on kitkat still? You should get lolipop by now..
Click to expand...
Click to collapse
Yes i am now at 5.1.1. Is there anyway i can unlock my bootloader?
abdullah.ahsan11 said:
Yes i am now at 5.1.1. Is there anyway i can unlock my bootloader?
Click to expand...
Click to collapse
Go into Settings, About Phone, tap Build Number 7 times, then go back one screen to Developer Options, enable Allow Bootloader Unlock, and USB Debugging.
Boot into Bootloader Mode and try:
fastboot oem unlock
That may not work on your phone.
Try to get the unlock code from Motorola:
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
If you are able to unlock the bootloader, you have two choices: you can flash the 6.0 stock firmware from another variant, or you can flash a MarshMallow ROM, such as CyanogenMod.
Here's a link to stock Moto X 2014 firmwares:
https://mega.nz/#F!ow8igZRL!Z7vmN8GOpez2bVMYDvEKkg
abdullah.ahsan11 said:
Yes i am now at 5.1.1. Is there anyway i can unlock my bootloader?
Click to expand...
Click to collapse
Your bootloader is locked. To unlock it you need to use kingroot, then sunshine to unlock it. After that you can flash a marshmallow rom.
Sent from my XT1095 using Tapatalk
AGISCI said:
Your bootloader is locked. To unlock it you need to use kingroot, then sunshine to unlock it. After that you can flash a marshmallow rom.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
I am a noob . Can You please refer me a link/tutorial. I know about king root but sunshine is new to me
UPDATE:
I tried to root with kingroot and it failed
For links to relevant guides and tutorials see Tony Stark's sticky at the top of the general forum.
Hi Sir, Gus Ghanem, pleased take two minutes to help me
Gus Ghanem said:
Go into Settings, About Phone, tap Build Number 7 times, then go back one screen to Developer Options, enable Allow Bootloader Unlock, and USB Debugging.
Boot into Bootloader Mode and try:
fastboot oem unlock
That may not work on your phone.
Try to get the unlock code from Motorola:
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
If you are able to unlock the bootloader, you have two choices: you can flash the 6.0 stock firmware from another variant, or you can flash a MarshMallow ROM, such as CyanogenMod.
Here's a link to stock Moto X 2014 firmwares:
https://mega.nz/#F!ow8igZRL!Z7vmN8GOpez2bVMYDvEKkg
Click to expand...
Click to collapse
Dear sir,
I have Verizon xt 1096 and want to install Android 6.0 from other variants like xt 1092 from stock firmwares which links that you provided above. I will unlock my bootloader.
You please guide me how I can install using fastboot on my windows PC. I don't care about CDMA, it should work on GSM networks 2G and UMTS 3G and LTE because now I am in UAE and not using Verizon.
I need marshmallow 6.0. ... and I don't want to install custom recovery, ROM or root it, if it not necessary for upgrade process.
I will be very thankful to you.
Sorry I forgotten to mention, now I am on stock 5.1
Please also post some commands for fastboot. Thanks
abrarakram19 said:
Dear sir,
I have Version xt 1096 and want to install Android 6.0 from other Version like xt 1092 from stock firmwares which links that you provided above. I will unlock my bootloader.
You please guide me how I can install using fastboot on my windows PC. I don't care about CDMD, it should work on GSM networks 2G and 3G because now I am in UAE and not using Verizon.
I need marshmallow 6.0. ... and I don't want to install custom recovery, ROM or root it, if is it not necessary for upgrade process.
I will be very thankful to you.
Click to expand...
Click to collapse
Install Motorola USB drivers:
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
Extract/unzip the firmware file. Put adb.exe, fastboot.exe, AdbWinApi.dll, AdbWinUsbApi.dll inside that folder with the firmware files. Shift + Right click in the folder, and select Open command window here, paste these commands:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
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 system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
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
Gus Ghanem said:
Install Motorola USB drivers:
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
Extract/unzip the firmware file. Put adb.exe, fastboot.exe, AdbWinApi.dll, AdbWinUsbApi.dll inside that folder with the firmware files. Shift + Right click in the folder, and select Open command window here, paste these commands:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
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 system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
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
Click to expand...
Click to collapse
Thank you very much sir. I will try and I hope it will be done with your cooperation. If I felt any trouble I will beg some help from you. Thanks again.
Gus Ghanem said:
Install Motorola USB drivers:
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
Extract/unzip the firmware file. Put adb.exe, fastboot.exe, AdbWinApi.dll, AdbWinUsbApi.dll inside that folder with the firmware files. Shift + Right click in the folder, and select Open command window here, paste these commands:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
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 system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
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
Click to expand...
Click to collapse
Great sir, I followed your instructions and I successfully upgraded my moto x2 xt 1096 (5.1) to official 6.0 xt1092 without any trouble or changing my recovery or any thing else. Thanks for your help.
one thing is when I restart my device one warning screen appear like (your device's bootloader is unlocked and some more cautions) and moto boot animation is changed. Is it possible to get rid from these by simply re locking bootloader by fastboot command....... "fastboot oem lock"
Or after changing firmware it's not possible to re lock it simply myself or any other code is required.
And one more question can i later install other update like 6.0.1 if it is available in same way or will you upload any future updated firmware in same location MEGA from where I downloaded earlier.
And will I get any future OTA from Motorola i.e. 6.0.1 or higher and should I install that OTA if arrives, or not?
I will wait for your reply. Thank again
abrarakram19 said:
Great sir, I followed your instructions and I successfully upgraded my moto x2 xt 1096 (5.1) to official 6.0 xt1092 without any trouble or changing my recovery or any thing else. Thanks for your help.
one thing is when I restart my device one warning screen appear like (your device's bootloader is unlocked and some more cautions) and moto boot animation is changed. Is it possible to get rid from these by simply re locking bootloader by fastboot command....... "fastboot oem lock"
or after changing firmware it's not possible to re lock it simply myself or any other code is required.
And one more question can i later install other update like 6.0.1 if it is available in same way or will you upload any futur updated firmware in same location MEGA from where I downloaded earlier.
I will wait for your reply. Thank again
Click to expand...
Click to collapse
Yes, when you unlock your bootloader, the boot logo changes to the warning logo, and the boot animation was changed by Motorola for 6.0.
You should be able to relock the bootloader by "fastboot oem lock". You can also flash a different boot logo and animation, but then the phone will not be pure stock anymore.
Because you flashed pure stock firmware, you should get System updates for XT1092 when they are released by Motorola, you don't need to reflash the full firmware.
The factory firmwares on MEGA are not mine, but thank you to whoever is uploading them there.
Gus Ghanem said:
Yes, when you unlock your bootloader, the boot logo changes to the warning logo, and the boot animation was changed by Motorola for 6.0.
You should be able to relock the bootloader by "fastboot oem lock". You can also flash a different boot logo and animation, but then the phone will not be pure stock anymore.
Because you flashed pure stock firmware, you should get System updates for XT1092 when they are released by Motorola, you don't need to reflash the full firmware.
The factory firmwares on MEGA are not mine, but thank you to whoever is uploading them there.
Click to expand...
Click to collapse
Thanks dear Sir for your guidance.
So it mean if I re lock the bootloader by entering command "fastboot oem lock", then I can install future OTA update if it arrives for xt1092 without bricking my device? Or my device has official stock but hybrid firmware or some parts of firmware. (xt1096 +xt1092) and may brick while installing official motorola OTAs? Or now it is 100% pure xt1092.?
This is last request And I don't wat to waste your time any more because you already given your precious time to me.
Thanks again for your guidance.
abrarakram19 said:
Thanks dear Sir for your guidance.
So it mean if I re lock the bootloader by entering command "fastboot oem lock", then I can install future OTA update if it arrives for xt1092 without bricking my device? Or my device has official stock but hybrid firmware or some parts of firmware. (xt1096 +xt1092) and may brick while installing official motorola OTAs? Or now it is 100% pure xt1092.?
This is last request And I don't wat to waste your time any more because you already given your precious time to me.
Thanks again for your guidance.
Click to expand...
Click to collapse
1) You don't need to lock the bootloader to receive ota updates. Updates work with the bootloader unlocked.
2) Don't worry about updates, Motorola said marshmallow 6.0 is the last update this phone gets. There will not be anymore OTA updates.
Sent from my XT1095 using Tapatalk
abrarakram19 said:
Thanks dear Sir for your guidance.
So it mean if I re lock the bootloader by entering command "fastboot oem lock", then I can install future OTA update if it arrives for xt1092 without bricking my device? Or my device has official stock but hybrid firmware or some parts of firmware. (xt1096 +xt1092) and may brick while installing official motorola OTAs? Or now it is 100% pure xt1092.?
This is last request And I don't wat to waste your time any more because you already given your precious time to me.
Thanks again for your guidance.
Click to expand...
Click to collapse
Hi sir I tried to re lock the bootloader by entering command " fastboot oem lock " and failed as........
..... (bootloader) FAIL: please run fastboot oem lock begin first!
(bootloader) sst lock failure!
Then I entered... fastboot oem lock begin
and returnd string is follow
.... ( bootloader ) ready to flash signed images
Then I can't understand what to do now.?
And an other thing when I connect my phone to PC it is still recognise and mention it's name XT 1096 however I installed firmware of XT 1092 and every thing inside is totally new corresponding to 6.0 and is XT 1092.
Is there any thing wrong, or its bootloader could be re locked. Or I should repeat the whole flashing process and at last befor entering "fastboot reboot", I should try fastboot oem lock. Is that maters or not before rebooting first time, or should I re flash the boot.img now to lock the bootloader or it is more difficult to do or it is impossible. Any idea or help or any other link please.
---------- Post added at 04:10 PM ---------- Previous post was at 04:10 PM ----------
abrarakram19 said:
Thanks dear Sir for your guidance.
So it mean if I re lock the bootloader by entering command "fastboot oem lock", then I can install future OTA update if it arrives for xt1092 without bricking my device? Or my device has official stock but hybrid firmware or some parts of firmware. (xt1096 +xt1092) and may brick while installing official motorola OTAs? Or now it is 100% pure xt1092.?
This is last request And I don't wat to waste your time any more because you already given your precious time to me.
Thanks again for your guidance.
Click to expand...
Click to collapse
Hi sir I tried to re lock the bootloader by entering command " fastboot oem lock " and failed as........
..... (bootloader) FAIL: please run fastboot oem lock begin first!
(bootloader) sst lock failure!
Then I entered... fastboot oem lock begin
and returnd string is follow
.... ( bootloader ) ready to flash signed images
Then I can't understand what to do now.?
And an other thing when I connect my phone to PC it is still recognise and mention it's name XT 1096 however I installed firmware of XT 1092 and every thing inside is totally new corresponding to 6.0 and is XT 1092.
Is there any thing wrong, or its bootloader could be re locked. Or I should repeat the whole flashing process and at last befor entering "fastboot reboot", I should try fastboot oem lock. Is that maters or not before rebooting first time, or should I re flash the boot.img now to lock the bootloader or it is more difficult to do or it is impossible. Any idea or help or any other link please.
---------- Post added at 04:17 PM ---------- Previous post was at 04:10 PM ----------
AGISCI said:
1) You don't need to lock the bootloader to receive ota updates. Updates work with the bootloader unlocked.
2) Don't worry about updates, Motorola said marshmallow 6.0 is the last update this phone gets. There will not be anymore OTA updates.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
Hi sir I tried to re lock the bootloader by entering command " fastboot oem lock " and failed as........
..... (bootloader) FAIL: please run fastboot oem lock begin first!
(bootloader) sst lock failure!
Then I entered... fastboot oem lock begin
and returnd string is follow*
.... ( bootloader ) ready to flash signed images
Then I can't understand what to do now.
And an other thing when I connect my phone to PC it is still recognise and mention it's name XT 1096 however I installed firmware of XT 1092 and every thing inside is totally new corresponding to 6.0 and is XT 1092.*
Is there any thing wrong, or its bootloader could be re locked. Or I should repeat the whole flashing process and at last befor entering "fastboot reboot", I should try fastboot oem lock. Is that maters or not before rebooting first time, or should I re flash the boot.img now to lock the bootloader or it is more difficult to do or it is impossible. Any idea or help or any other link please. Actually I hate this warnings screen and cautions every time when I power on my device and moto boot animation is terrible since I unlocked the bootloader.
verizon unlocked device.
sir i have an unlocked verizon moto x 2nd generation. can i get official motorola 6.0 update? is there any way?
thanks
Yes sure, follow the instructions in first page of this thread given by Gus Ghanem and say thanks to XDA developer team and their members
---------- Post added at 02:19 PM ---------- Previous post was at 02:15 PM ----------
There is also a MEGA link to download stock marshmallow 6.0 firmwares
---------- Post added at 02:25 PM ---------- Previous post was at 02:19 PM ----------
But only proceed to flash marshmallow 6.0 firmwares if you are not using Verizon network because you will loose CDMA but you can use GSM and UMTS networks
abrarakram19 said:
Yes sure, follow the instructions in first page of this thread given by Gus Ghanem and say thanks to XDA developer team and their members
---------- Post added at 02:19 PM ---------- Previous post was at 02:15 PM ----------
There is also a MEGA link to download stock marshmallow 6.0 firmwares
---------- Post added at 02:25 PM ---------- Previous post was at 02:19 PM ----------
But only proceed to flash marshmallow 6.0 firmwares if you are not using Verizon network because you will loose CDMA but you can use GSM and UMTS networks
Click to expand...
Click to collapse
For those who use verizon service there is this rom:
http://forum.xda-developers.com/showthread.php?t=3327345
Verizon cdma works in this custom stock rom.
Sent from my XT1095 using Tapatalk
Hi,
i just got brand new unused Moto X 2nd gen (2014), It has 4.4 Android on it, but OTA update does not want to work anymore, as of 15.1.2020.
It is unlocked XT1095.
I am looking for somebody to help me over Skype to update it to 5.1 and then to 6.0 - the way usual update would go, and would donate to you via PayPal.
i was following this guide https://forum.xda-developers.com/moto-e5/how-to/guide-root-twrp-moto-e5-play-explained-t3856182 and i did everything up until "fastboot flash recovery twrp_james.img
fastboot reboot recovery" and it says the image isnt signed or corrupted any help would be nice thanks.
skyrimman33 said:
i was following this guide https://forum.xda-developers.com/moto-e5/how-to/guide-root-twrp-moto-e5-play-explained-t3856182 and i did everything up until "fastboot flash recovery twrp_james.img
fastboot reboot recovery" and it says the image isnt signed or corrupted any help would be nice thanks.
Click to expand...
Click to collapse
Have you successfully unlocked bootloader?..I get same error messages when flashing on e5 play with unlockable bootloader..Motorola will not add the Verizon James variant to oem unlock list..but a locked bootloader will give you that error message..