Related
Hey,
I got my Moto G like 3 Weeks ago, unlocked it and rooted it. Now there is an OTA that my friend got. (He's not unlocked). I am not recieving this OTA Update at all and i cant relock my Bootloader.
When i flash stock Firmware with fastboot, starting with OEM Lock begin, i get an error. The first error comes when i flash something. It does flash it without problems but says <Bootloader> Preflash Validation failed. I am sure that i am using the right Firmware, i think it's not signed. So, the last command i run is OEM Lock wich gives me the error SST Lock failure. And then it flashed to stock, everything fine but it's not locked again. Also there is no recovery when i press recovery on bootloader. On my Nexus 5 i got an Recovery and not an android with a red sign laying on the ground...
How can i relock my Bootloader and where to get official signed images for XT1068 Dual SIM Version (Germany) (used theese, getting errors sbf .droid-developers. org/phone.php?device=36)
I could not find anything regarding this in search, sorry.
And sorry for that TERRIBLE english but greetings from germany
tbunlmtd said:
Hey,
I got my Moto G like 3 Weeks ago, unlocked it and rooted it. Now there is an OTA that my friend got. (He's not unlocked). I am not recieving this OTA Update at all and i cant relock my Bootloader.
When i flash stock Firmware with fastboot, starting with OEM Lock begin, i get an error. The first error comes when i flash something. It does flash it without problems but says <Bootloader> Preflash Validation failed. I am sure that i am using the right Firmware, i think it's not signed. So, the last command i run is OEM Lock wich gives me the error SST Lock failure. And then it flashed to stock, everything fine but it's not locked again. Also there is no recovery when i press recovery on bootloader. On my Nexus 5 i got an Recovery and not an android with a red sign laying on the ground...
How can i relock my Bootloader and where to get official signed images for XT1068 Dual SIM Version (Germany) (used theese, getting errors sbf .droid-developers. org/phone.php?device=36)
I could not find anything regarding this in search, sorry.
And sorry for that TERRIBLE english but greetings from germany
Click to expand...
Click to collapse
First of all: you do have a recovery. The android with the red exclamation mark laying on the ground IS your recovery. But it's not really designed for common users. To get the options in recovery (when you're in the screen with the android with the red exlamation mark), hold the VOLUME-UP for 10 to 15 seconds an then pres the POWER button. And there you have it: a recovery!
About the relock of the bootloader: the rom has to be flashed without errors to have a possible relock. Flash a rom with a higher or the same build number!
I myself had a lot of troubles with this too, but in the end I flashed the RETAILDSDSALL_XT1068_4.4.4_KXB21.85-27_cid7_CFC_SVC.xml.zip and after that i had a succesfull relock!
By the way I used the fastboot under Linux-Ubuntu. But it should work with mfastboot in Windows too, i suppose!
Greetings from Holland!
smitharro said:
First of all: you do have a recovery. The android with the red exclamation mark laying on the ground IS your recovery. But it's not really designed for common users. To get the optionsin recovery (when you're in the screen with the android with the red exlamation mark), hold the VOLUME-UP for 10 to 15 seconds an then pres the POWER button. And there you have it: a recovery!
About the relock of the bootloader: the rom has to be flashed without errors to have a possible relock. Flash a rom with a higher or the same build number!
I myself had a lot of troubles with this too, but in the end I flashed the RETAILDSDSALL_XT1068_4.4.4_KXB21.85-27_cid7_CFC_SVC.xml.zip and after that i had a succesfull relock!
By the way I used the fastboot under Linux-Ubuntu. But it should work with mfastboot in Windows too i suppose!
Greetings from Holland!
Click to expand...
Click to collapse
Thank you, i'll try this now!
Working just fine, thanks!
Cannot lock bootloader
tbunlmtd said:
Working just fine, thanks!
Click to expand...
Click to collapse
I am stuck here too. Cannot relock bootloader ...
build version KXB21.85-17; System version: Blur_Version.21.11.17.titan_retuglb.retuglb.en.US
I have downloaded the same firmware from http://sbf.droid-developers.org/phone.php?device=36
Applied flash according to :
mfastboot.exe oem lock begin
mfastboot.exe flash partition gpt.bin
mfastboot.exe flash motoboot motoboot.img
mfastboot.exe flash logo logo.bin
mfastboot.exe flash boot boot.img
mfastboot.exe flash recovery recovery.img
mfastboot.exe flash system system.img_sparsechunk.0
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
mfastboot.exe flash system system.img_sparsechunk.3
mfastboot.exe flash modem NON-HLOS.bin
mfastboot.exe erase modemst1
mfastboot.exe erase modemst2
mfastboot.exe flash fsg fsg.mbn
mfastboot.exe erase cache
mfastboot.exe erase userdata
mfastboot.exe oem lock
Click to expand...
Click to collapse
getting downgrade error, Invalid PIV signed image error, sst lock failure error ! failed to validate system image in device display
[NB: I have changed to US version (retuaws) before and flashed back to global ]
Same Exact problem
Anonymous 360 said:
I am stuck here too. Cannot relock bootloader ...
build version KXB21.85-17; System version: Blur_Version.21.11.17.titan_retuglb.retuglb.en.US
I have downloaded the same firmware from http://sbf.droid-developers.org/phone.php?device=36
Applied flash according to :
getting downgrade error, Invalid PIV signed image error, sst lock failure error ! failed to validate system image in device display
[NB: I have changed to US version (retuaws) before and flashed back to global ]
Click to expand...
Click to collapse
I am usually quite good at following directions, but after unlocking this thing, I am trying to relock it so I can download Lollipop and I get the exact same errors. I have been on it for 5 hours and counting.
What am I doing wrong?
Damionix said:
I am usually quite good at following directions, but after unlocking this thing, I am trying to relock it so I can download Lollipop and I get the exact same errors. I have been on it for 5 hours and counting.
What am I doing wrong?
Click to expand...
Click to collapse
if you cannot fix it yet, then let me know.
Look at my post here. I don't want to make duplicate posts. Therefore a link!
So I just bought my Moto G 2014 (unlocked) and I have it all activated and set up. I was wondering though when Lollipop will be pushed so I can update to it? All I see articles are saying "It will get it" and "you should be able to update to it now" but I can't and I really don't want to void my warranty a day after I bought the phone. I want to try vanilla* Lollipop. Does anybody know when exactly?
( * = without having to manually install it via unlocking bootloader and using fastboot)
Motorola knows.
If it is the XT1063/4 ones, you can already install it via OTA.
Sent from my XT1064 using XDA Free mobile app
I have an Xt1064 and I still havent received the update. Is the update available here the same as the OTA? Im tempted to just install that one.
PerrottiX said:
If it is the XT1063/4 ones, you can already install it via OTA.
Sent from my XT1064 using XDA Free mobile app
Click to expand...
Click to collapse
I have XT1063 and I still didn't get the update through OTA as well. Is this normal?
i was trying
Hello, im from Perú. I got an XT1063 so when i am flashing i got two problems
1. hab check failed for boot
2. hab check failed for recovery
so anyone can help me?
I tried with Fastboot and with mfastboot, but same result.
I found this updates in other web which you can update to lollipop. Can anybody try them? I want to try but i can open the recovery...
getmovil dot com / motorola / root-moto-g-2014-android-lollipop /comment-page-1 /#comment-83348
Download the proper ota zip for your version from xda. Reboot into your stock bootloader. Apply update from sdcard. Done. No need to root or use fastboot. This can only be done on a completely stock phone with a locked bootloader. Its the same as end result that you'd get if you wait for the ota to arrive normally. Do not do this if you have unlocked your bootloader at any time. And make sure you use the proper ota zip for your model, there are three different models, the single sim us model ends in 1064.
Lokke9191 said:
Download the proper ota zip for your version from xda. Reboot into your stock bootloader. Apply update from sdcard. Done. No need to root or use fastboot. This can only be done on a completely stock phone with a locked bootloader. Its the same as end result that you'd get if you wait for the ota to arrive normally. Do not do this if you have unlocked your bootloader at any time. And make sure you use the proper ota zip for your model, there are three different models, the single sim us model ends in 1064.
Click to expand...
Click to collapse
...from where can i download the proper ota zip????
mine is MOTO G2 (2nd GEN) XT1068 dual sim europe
You can't. Lollipop isn't released for the XT1068 yet. But be patient. I suspect it to be there in the first or the second quarter of 2015! (And with a little luck maybe even this year...).
i understood we will take directly :angel:Android 6.0 (M) Milky Bar.......:good:
htcgr said:
i understood we will take directly :angel:Android 6.0 (M) Milky Bar.......:good:
Click to expand...
Click to collapse
Honestly, it should be there anytime now. But people keep asking the question over and over again: when is it coming? This is annoying, because no one really knows!
Lokke9191 said:
Download the proper ota zip for your version from xda. Reboot into your stock bootloader. Apply update from sdcard. Done. No need to root or use fastboot. This can only be done on a completely stock phone with a locked bootloader. Its the same as end result that you'd get if you wait for the ota to arrive normally. Do not do this if you have unlocked your bootloader at any time. And make sure you use the proper ota zip for your model, there are three different models, the single sim us model ends in 1064.
Click to expand...
Click to collapse
any idea how to re-lock the bootloader? :good:
kevin_arthur said:
any idea how to re-lock the bootloader? :good:
Click to expand...
Click to collapse
Follow the guide at ( http://www.droidviews.com/restore-moto-g-2014-to-stock-and-lock-the-bootloader/ ). However there's a couple of things you have to do differently.
Your first command after you enter fastboot mode is gonna have to be "mfastboot.exe oem lock begin".
Theres also gonna be four system.img that you have to flash so after the command "mfastboot.exe flash system system.img_sparsechunk.2" you have to enter the command "mfastboot.exe flash system system.img_sparsechunk.3". Follow the rest of the guide, including the "mfastboot.exe oem lock" command at the end.
So basically the commands would be...
mfastboot.exe oem lock begin
mfastboot.exe flash partition gpt.bin
mfastboot.exe flash motoboot motoboot.img
mfastboot.exe flash logo logo.bin
mfastboot.exe flash boot boot.img
mfastboot.exe flash recovery recovery.img
mfastboot.exe flash system system.img_sparsechunk.0
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
mfastboot.exe flash system system.img_sparsechunk.3
mfastboot.exe flash modem NON-HLOS.bin
mfastboot.exe erase modemst1
mfastboot.exe erase modemst2
mfastboot.exe flash fsg fsg.mbn
mfastboot.exe erase cache
mfastboot.exe erase userdata
mfastboot.exe oem lock
My phone automatically rebooted after that last command and my boot loader was locked even though it still displays the "Bootloader Unlocked" screen, I was able to flash the zip in the OP through the stock recovery after that.
COPIED AND PASTED FROM ANOTHER THREAD.
Courtesy of captivatingtab
---------- Post added at 11:29 AM ---------- Previous post was at 11:13 AM ----------
htcgr said:
...from where can i download the proper ota zip????
mine is MOTO G2 (2nd GEN) XT1068 dual sim europe
Click to expand...
Click to collapse
The xt1068 ota isnt available yet. There is a process to install another versions firmware on the xt1068 then upgrade to lollipop. But it looks buggy and super risky. I wouldn't recommend trying it. Id wait a little for the 1068 ota to be released. I know the other poster said it wont be available until 2015. But nobody knows for sure when itll be out. If i where to guess, id say itll be out fairly soon, sometime in the next 30 days. If I where you Id play it safe and wait it out.
---------- Post added at 11:32 AM ---------- Previous post was at 11:29 AM ----------
The only otas out so far are for the 1064 & 1063.
wish me luck!
Lokke9191 said:
Follow the guide at ( ). However there's a couple of things you have to do differently.
Your first command after you enter fastboot mode is gonna have to be "mfastboot.exe oem lock begin".
Theres also gonna be four system.img that you have to flash so after the command "mfastboot.exe flash system system.img_sparsechunk.2" you have to enter the command "mfastboot.exe flash system system.img_sparsechunk.3". Follow the rest of the guide, including the "mfastboot.exe oem lock" command at the end.
So basically the commands would be...
mfastboot.exe oem lock begin
mfastboot.exe flash partition gpt.bin
mfastboot.exe flash motoboot motoboot.img
mfastboot.exe flash logo logo.bin
mfastboot.exe flash boot boot.img
mfastboot.exe flash recovery recovery.img
mfastboot.exe flash system system.img_sparsechunk.0
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
mfastboot.exe flash system system.img_sparsechunk.3
mfastboot.exe flash modem NON-HLOS.bin
mfastboot.exe erase modemst1
mfastboot.exe erase modemst2
mfastboot.exe flash fsg fsg.mbn
mfastboot.exe erase cache
mfastboot.exe erase userdata
mfastboot.exe oem lock
My phone automatically rebooted after that last command and my boot loader was locked even though it still displays the "Bootloader Unlocked" screen, I was able to flash the zip in the OP through the stock recovery after that.
COPIED AND PASTED FROM ANOTHER THREAD.
Courtesy of captivatingtab
Click to expand...
Click to collapse
okey, i will try.
thank you my friend!
smitharro said:
You can't. Lollipop isn't released for the XT1068 yet. But be patient. I suspect it to be there in the first or the second quarter of 2015! (And with a little luck maybe even this year...).
Click to expand...
Click to collapse
It'll be sooner than that. Within the next 6 weeks.
Sent from my XT1068 using XDA Free mobile app
Lokke9191 said:
Download the proper ota zip for your version from xda. Reboot into your stock bootloader. Apply update from sdcard. Done. No need to root or use fastboot. This can only be done on a completely stock phone with a locked bootloader. Its the same as end result that you'd get if you wait for the ota to arrive normally. Do not do this if you have unlocked your bootloader at any time. And make sure you use the proper ota zip for your model, there are three different models, the single sim us model ends in 1064.
Click to expand...
Click to collapse
i have the international unlocked xt1063. where can i get the zip?
Is there any official source on the release date?
Kobro said:
i have the international unlocked xt1063. where can i get the zip?
Click to expand...
Click to collapse
Its in the general section under a thread titled ota-index 1063-1064 update to lollipop.
I have a complete stock, nothing flashed or rooted or anything xt1064 and it says the zip needs a fingerprint when I try to install it from this thread...
http://forum.xda-developers.com/moto-g-2014/development/lollipop-moto-g-2014-xt1064-t2937361/page11
htcgr said:
i understood we will take directly :angel:Android 6.0 (M) Milky Bar.......:good:
Click to expand...
Click to collapse
its a Marshmallow 6.0
Hi I been flashing the CM 12.1 nightlies, starting from the mexican 5.0.2 stock firmware for a while. Suddenly, the power button and the screen got unresponsive.... i've tried to flash back to stock several times, either kitkat or lollipop, with the same results... The only different thing I noticed was when I started the bootloader menu the baseband line was empty. One of the times I flashed to stock it came back and start working correctly, but when I flashed CM again the same thing happened.
Now I have the baseband line black and the OS keeps crushing....
I tried flashing the radio only with the same results....
Any thoughts?
PS: RSD lite 6.2.4 doesn't recognize my devices so I flash with cmd and mfastboot using these commands:
mfastboot getvar max-sparse-size
mfastboot flash motoboot bootloader.img
mfastboot flash radio radio.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash 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 erase cache
mfastboot erase userdata
mfastboot erase clogo
mfastboot oem fb_mode_clear
mfastboot reboot
Please help!
I had a similar problem with my XT1254. I was using a modified stock 5.1 system image (since that's all we can do with our locked bootloaders...for now. Our hope lies with you, jcase and beaups!) and after months of using it without any issues, it crashed. I got it working again by using similar steps to what you did to flash 4.4.4, but with a few exceptions:
1. I used fastboot instead of mfastboot.
2. I flashed something called gbt.bin I think to the "partition" partition. I'll re-download the firmware that I used and confirm that. I was following the flash sequence in the full firmware's xml file.
3. When the phone finally booted (it seems like it took between 5-10 minutes), I went through the initial setup, and I noticed a notification that said "complete uninstall." I clicked on it, and it said that it wanted to restore the motorola sensor firmware to a previous version. I said okay, and it did whatever it needed to do and rebooted the phone.
Now the phone boots fine (phew), but the baseband line in the bootloader is still blank. It might be related, but I remember that the moto app and also the moto actions (I think?) app updated itself recently, so maybe that sensor firmware update is the cause of the problem?
EDIT: Here are my exact flash steps. Keep in mind that this is for a Droid Turbo, not the Moto Maxx that you must be using. I'm not sure if that matters.
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
fastboot flash system system.img_sparsechunk4
fastboot flash system system.img_sparsechunk5
fastboot flash system system.img_sparsechunk6
fastboot flash system system.img_sparsechunk7
fastboot erase ddr
fastboot erase cache
fastboot erase userdata
fastboot reboot
EDIT2: I set up my 5.1 image just to see if I could replicate the crash and sure enough, once I updated Moto Actions, everything fell apart.
TheSt33v said:
I had a similar problem with my XT1254. I was using a modified stock 5.1 system image (since that's all we can do with our locked bootloaders...for now. Our hope lies with you, jcase and beaups!) and after months of using it without any issues, it crashed. I got it working again by using similar steps to what you did to flash 4.4.4, but with a few exceptions:
1. I used fastboot instead of mfastboot.
2. I flashed something called gbt.bin I think to the "partition" partition. I'll re-download the firmware that I used and confirm that. I was following the flash sequence in the full firmware's xml file.
3. When the phone finally booted (it seems like it took between 5-10 minutes), I went through the initial setup, and I noticed a notification that said "complete uninstall." I clicked on it, and it said that it wanted to restore the motorola sensor firmware to a previous version. I said okay, and it did whatever it needed to do and rebooted the phone.
Now the phone boots fine (phew), but the baseband line in the bootloader is still blank. It might be related, but I remember that the moto app and also the moto actions (I think?) app updated itself recently, so maybe that sensor firmware update is the cause of the problem?
EDIT: Here are my exact flash steps. Keep in mind that this is for a Droid Turbo, not the Moto Maxx that you must be using. I'm not sure if that matters.
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
fastboot flash system system.img_sparsechunk4
fastboot flash system system.img_sparsechunk5
fastboot flash system system.img_sparsechunk6
fastboot flash system system.img_sparsechunk7
fastboot erase ddr
fastboot erase cache
fastboot erase userdata
fastboot reboot
EDIT2: I set up my 5.1 image just to see if I could replicate the crash and sure enough, once I updated Moto Actions, everything fell apart.
Click to expand...
Click to collapse
EDIT3: I just noticed that on Rootjunky's video, his baseband appears blank too, so maybe it was always blank and we just didn't notice before.
---------- Post added at 10:39 AM ---------- Previous post was at 09:41 AM ----------
Did you ever fix your problem? If so, how? Because my phone is messing up again and my previous method isn't working.
TheSt33v said:
EDIT3: I just noticed that on Rootjunky's video, his baseband appears blank too, so maybe it was always blank and we just didn't notice before.
---------- Post added at 10:39 AM ---------- Previous post was at 09:41 AM ----------
Did you ever fix your problem? If so, how? Because my phone is messing up again and my previous method isn't working.
Click to expand...
Click to collapse
Yeah I was Ok for a few days without the moto updates, but then it started crashing again... I don't know how to fix it... the baseband keeps going on and off in the fastboot mode and everytime it goes off the problem arise
andrescarre87 said:
Yeah I was Ok for a few days without the moto updates, but then it started crashing again... I don't know how to fix it... the baseband keeps going on and off in the fastboot mode and everytime it goes off the problem arise
Click to expand...
Click to collapse
That's weird. I got a warranty replacement from Motorola that appeared to be brand new and before I modified it, I checked the bootloader. Baseband was blank. So even on a stock, unmodified phone, it can be blank. Here's my thread that details everything that I tried to fix this problem: http://forum.xda-developers.com/droid-turbo/help/complicated-problem-restore-doesnt-help-t3184251. I managed to temporarily fix it, but it always broke again once I reflashed 5.1. I posted the system image that I made that temporarily fixed the problem, but remember that is for an XT1254, so I don't think it will work for you.
Hello Sir
I was about to update to computerfreak's .49 rom (version 1.37 that is). Prior to that I wanted to update to the latest modem, So i flashed the modem cleaner, and then the radio from firstencounter's thread
(http://forum.xda-developers.com/droid-turbo/development/droid-turbo-xt1254-bootloader-radio-t3259327)
Since then my baseband is unknown. I can't connect to wifi and my sim isn't being read
You seem to have fixed the problem? I was on computerfreaks 1.35 till now with no issues (except GPS wouldn't lock)
Hi all.
I just wanted to share my finding regarding this problem.
I realise that this may not fix the problem for everyone, but searching the forum, I have found MANY folks that have tried all the things that I have to no avail..
So I am posting this in hope that some of them might see this and hopefully cure their "Unknown Baseband", "No IMEI" and "No SIM card"
I recently upgraded to RR Marshmallow witch fixed some other problems I have had with my XT1254 Droid Turbo (Bluetooth related)
I also upgraded my Radio.img from 02r to 03r (44 to 49?)
While this fixed my Bluetooth problems and everything was running really well for 2-3 days, out of nowhere, in the middle of a phone call, I got: No IMEI, Unknown Baseband and no SIM card...
I searched the forum (and google) and have tried just about everything..
Upgrade / downgrade firmware
Install stock rom
Backup/restore EFS / IMEI partition
Different radios
A few third party programs
Loads of ADB commands (learned a lot in the process though!)
I was kinda ready to give up and buy a new phone, so I thought I might as well try something daring WITCH FIXED MY PROBLEM!!!
I sprayed a little electrical cleaner into the SIM slot and let it dry out. When I pushed in the SIM card, I felt some resistance that definitely wasn't there before! I know this for sure because I removed / inserted the SIM card a LOT of times to see if it would connect.
My guess is that there is a mechanism that pushes the SIM connection points away from the SIM card when it is being pushed in, and when it is al the way in, it will snap back up against the card. (or some other mechanism that tells the phone that a SIM card has been inserted. I don't know)
This mechanism must have gotten stuck and the cleaner must have removed whatever was keeping it from moving.
I DO NOT recommend people doing this, since it may damage your device (I suppose if you are really unlucky, it might even blow up your battery?¿)
A more gentle approach would be to pray off the back cover (haven't tried this myself, but youtube suggest this is fairly easy) and clean / massage the mechanism in a more controlled manor.
Best of luck to all of you! I hope you find a fix for your problem!
^GaMbi
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.
Hi guys,
Hoping you lovely people can help.
I think I may have bricked my device.
It's stuck in a fastboot bootloop with the error code "failed to validate system image"
Now my (amateur) thinking of this is it's possibly due to the device now being OEM locked? Status 2. As I accidentally locked it like a fool.
I can't get into developer options to enable OEM unlock as it wont boot to system.
I've been going through all the forums and can't find any help.
Thank you all in advance
nickkk93 said:
Hi guys,
Hoping you lovely people can help.
I think I may have bricked my device.
It's stuck in a fastboot bootloop with the error code "failed to validate system image"
Now my (amateur) thinking of this is it's possibly due to the device now being OEM locked? Status 2. As I accidentally locked it like a fool.
I can't get into developer options to enable OEM unlock as it wont boot to system.
I've been going through all the forums and can't find any help.
Thank you all in advance
Click to expand...
Click to collapse
You are on stock ?
RolanDroid said:
You are on stock ?
Click to expand...
Click to collapse
I am now, I was using CM13
nickkk93 said:
Hi guys,
Hoping you lovely people can help.
I think I may have bricked my device.
It's stuck in a fastboot bootloop with the error code "failed to validate system image"
Now my (amateur) thinking of this is it's possibly due to the device now being OEM locked? Status 2. As I accidentally locked it like a fool.
I can't get into developer options to enable OEM unlock as it wont boot to system.
I've been going through all the forums and can't find any help.
Thank you all in advance
Click to expand...
Click to collapse
I had the same problem when flashed back the stock recovery, flashed UK or DE over EU stock+twrp
Those are the latest XT1072 stocks, get the one you prefer and flash it.
GB->http://www.filefactory.com/file/42o...B22.99-24.12_cid7_subsidy-DEFAULT_CFC.xml.zip
ES->http://www.filefactory.com/file/2aj...B22.99-24.12_cid7_subsidy-DEFAULT_CFC.xml.zip
DE->http://www.filefactory.com/file/1hr...B22.99-24.12_cid7_subsidy-DEFAULT_CFC.xml.zip
EU->http://www.filefactory.com/file/57j...B22.99-24.12_cid7_subsidy-DEFAULT_CFC.xml.zip
Get fastboot + mfastbootv2(http://forum.xda-developers.com/attachment.php?attachmentid=2427667) and flash the fw like this
mfastboot flash partition gpt.bin
mfastboot flash bootloader bootloader.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
Click to expand...
Click to collapse
If you want also to restory factory/delete data
mfastboot erase cache
mfastboot erase userdata
Click to expand...
Click to collapse
and then
mfastboot reboot
Click to expand...
Click to collapse
You should be ok now, no need to lock/unlock if you get the right region fw for your phone.
dr.nic said:
I had the same problem when flashed back the stock recovery, flashed UK or DE over EU stock+twrp
Those are the latest XT1072 stocks, get the one you prefer and flash it.
GB->http://www.filefactory.com/file/42o...B22.99-24.12_cid7_subsidy-DEFAULT_CFC.xml.zip
ES->http://www.filefactory.com/file/2aj...B22.99-24.12_cid7_subsidy-DEFAULT_CFC.xml.zip
DE->http://www.filefactory.com/file/1hr...B22.99-24.12_cid7_subsidy-DEFAULT_CFC.xml.zip
EU->http://www.filefactory.com/file/57j...B22.99-24.12_cid7_subsidy-DEFAULT_CFC.xml.zip
Get fastboot + mfastbootv2(http://forum.xda-developers.com/attachment.php?attachmentid=2427667) and flash the fw like this
If you want also to restory factory/delete data
and then
masftboot flash partition gpt.bin
You should be ok now, no need to lock/unlock if you get the right region fw for your phone.
Click to expand...
Click to collapse
When running the first command:
mfastboot flash partition gpt.bin
I'm getting the error:
(bootloader) Preflash validation failed
also getting
(bootloader) Invalid signed image
(bootloader) preflash validation failed
Merge whit thread http://forum.xda-developers.com/moto-g-lte/help/xt1072-stuck-fastboot-flash-screen-help-t3265735 same problem.
Check my reply in page 2 and see if that work for you.
Hi I seem to be having some major issues with my Xt1072 and cannot get it to boot!
It all started with the message popping up saying error creating mount script in second partition?
I got sick of this so I started rebooting the phone to see if I could rectify it?! and like before it just kept getting stuck in bootloop. then as the hours progressed it got worse and eventually i am at the point where my pc does not see it, then it sees it, then it doesnt see it? then I got my phone stuck in the weirdest loop Ive ever seen, it actually boots to the home screen, then 10 seconds later, screen goes black and then wakes up again and back to home screen, 10 seconds later the process gets repeated over and over again, the only thing that seems to stop it dead in its tracks is when I connect it to my pc and hold power and vol down simultaneously. now all it does sometimes is just goes straight to a white screen with huge battery charging and thats it?! i tried the commands which ive quoted below with the resulting cmd:getvar:max-sparse-size on the bootloader screen on my phone???? what does it all mean??? anyone know what the hell is going on??? I am at a loss??
If you want also to restory factory/delete data
Quote:
mfastboot erase cache
mfastboot erase userdata
and then
Quote:
mfastboot reboot
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot flash partition gpt.bin
< waiting for device >
target max-sparse-size: 256MB
error: cannot load 'gpt.bin': No error
Click to expand...
Click to collapse
Hi I have a problem related to this. The phone is not mine, but the owner has been doing things about rooting and that, and after touching things of the phone and reboot it, it was stuck on the motorola logo, I am able to use mfastboot, and I have followed the guides said in this post, but nothing works.
Could you help me?
Thanks.