endless bootloop after doing the OTA to 4.4.2 - Moto X Q&A

So one of my buddies took the OTA update for 4.4.2 while being rooted on 4.4 with TWRP as his recovery. Now he is stuck in an endless bootloop. Any idea what we could do to bring his phone back to life?
By the way, he is on Sprint and has his bootloader unlocked
Any advice would help!
Thanks.

AbstractXart said:
So one of my buddies took the OTA update for 4.4.2 while being rooted on 4.4 with TWRP as his recovery. Now he is stuck in an endless bootloop. Any idea what we could do to bring his phone back to life?
By the way, he is on Sprint and has his bootloader unlocked
Any advice would help!
Thanks.
Click to expand...
Click to collapse
This happened to me too.
Just flash the latest firmware for your device at http://sbf.droid-developers.org/phone.php?device=0
Then accept the OTA.
Re-install TWRP.
Hope this works for you too.

patspdaphone said:
This happened to me too.
Just flash the latest firmware for your device at http://sbf.droid-developers.org/phone.php?device=0
Then accept the OTA.
Re-install TWRP.
Hope this works for you too.
Click to expand...
Click to collapse
So to accept the OTA, did you go through the bootloader/recovery and flash it, or were you able to turn on your phone and accept it? Sorry I don't have his phone on me right now otherwise I would have done it .

Don't flash the full SBF..
boot the phone into fastboot mode... mfastboot erase cache... the reboot the phone. that will remove the OTA zip file from chache and stop the boot loop.
The bootloop is because the phone has TWRP on it rather than stock recovery.
To take the OTA properly, use mfastboot to reflash stock recovery only. Also have him undo any hacks that might have touched system files or the OTA will fail, (mfastboot system will also get /system back to normal)...

KidJoe said:
Don't flash the full SBF..
boot the phone into fastboot mode... mfastboot erase cache... the reboot the phone. that will remove the OTA zip file from chache and stop the boot loop.
The bootloop is because the phone has TWRP on it rather than stock recovery.
To take the OTA properly, use mfastboot to reflash stock recovery only. Also have him undo any hacks that might have touched system files or the OTA will fail, (mfastboot system will also get /system back to normal)...
Click to expand...
Click to collapse
We actually just ended up clearing the system cache and that seemed to do the trick .
I incredibly appreciate all the info! If anyone makes this silly mistake, all you need to do is clear the cache and everything works as intended.

AbstractXart said:
We actually just ended up clearing the system cache and that seemed to do the trick .
I incredibly appreciate all the info! If anyone makes this silly mistake, all you need to do is clear the cache and everything works as intended.
Click to expand...
Click to collapse
until the next time the OTA downloads and tries to install

I am having this very same problem. My phone just today went into boot loop. Running KangKat on unlocked 1053 with Faux kernel. No boot logo or anything. The phone just vibrates then after 30 seconds or so, it vibrates again. It does this non-stop.
I can plug my phone into USB and the phone's contents come up on my computer, but I can't get the screen to turn on!! Any ideas?

Globalrebel said:
I am having this very same problem. My phone just today went into boot loop. Running KangKat on unlocked 1053 with Faux kernel. No boot logo or anything. The phone just vibrates then after 30 seconds or so, it vibrates again. It does this non-stop.
I can plug my phone into USB and the phone's contents come up on my computer, but I can't get the screen to turn on!! Any ideas?
Click to expand...
Click to collapse
KangKat wtih Faux kernel? So you are not running the stock rom? I'm suprised the actually OTA installed.
I don't know anything about that rom, or kernel to begin to tell you how to fix this situation, short of reflashing your rom

KidJoe said:
KangKat wtih Faux kernel? So you are not running the stock rom? I'm suprised the actually OTA installed.
I don't know anything about that rom, or kernel to begin to tell you how to fix this situation, short of reflashing your rom
Click to expand...
Click to collapse
He probably flashed the "Flashable 4.4.2 ZIP" that is flashable through TWRP.
@Globalrebel :
You need to try to get into bootloader (AP Fastboot) mode. Try holding the VOL DOWN while the phone reboots (vibrates). Make sure the phone is unplugged from USB. If you can access fastboot, your best best would probably to flash the entire SBF back to stock.
Always check here first before you do something like trying to flash a stock update on a custom rom. We would have quickly informed you that this is ill-advised.
Good Luck

Ok, so I have held down the power button, and then when vibrating starts, I hold down vol down button. Then, it vibrates 2 times. What now? (Sorry, I'm freaked out as this is my only phones )
How can i check to see if it is actually in Fastboot mode? Since my screen doesn't show ANYTHING at all?
I started up an ADB server and connected my phone and tried "adb devices" but my phone isn't listed.
---------- Post added at 08:49 AM ---------- Previous post was at 08:40 AM ----------
samwathegreat said:
He probably flashed the "Flashable 4.4.2 ZIP" that is flashable through TWRP.
@Globalrebel :
You need to try to get into bootloader (AP Fastboot) mode. Try holding the VOL DOWN while the phone reboots (vibrates). Make sure the phone is unplugged from USB. If you can access fastboot, your best best would probably to flash the entire SBF back to stock.
Always check here first before you do something like trying to flash a stock update on a custom rom. We would have quickly informed you that this is ill-advised.
Good Luck
Click to expand...
Click to collapse
any ideas?
I just checked device manager and it shows "ADB Interface" and then MOT Single ADB Interface.
But its not showing up under devices when running command "ADB Devices" in CMD

Globalrebel said:
Ok, so I have held down the power button, and then when vibrating starts, I hold down vol down button. Then, it vibrates 2 times. What now? (Sorry, I'm freaked out as this is my only phones )
How can i check to see if it is actually in Fastboot mode? Since my screen doesn't show ANYTHING at all?
I started up an ADB server and connected my phone and tried "adb devices" but my phone isn't listed.
---------- Post added at 08:49 AM ---------- Previous post was at 08:40 AM ----------
any ideas?
Click to expand...
Click to collapse
Fastboot getvar all
If you get a response with that, proceed with the entire Sbf manual method as listed in the return to stock thread.

samwathegreat said:
Fastboot getvar all
If you get a response with that, proceed with the entire Sbf manual method as listed in the return to stock thread.
Click to expand...
Click to collapse
I got it to show some info after running the command. Now, I have the following guide open . .
[GUIDE][VIDEO] Moto X - Return to 100% stock (using RSD Lite OR manual flash)
But I don't see anything in RSDLite after running it and clicking "Show Device"
Can I just to the manual method?
For manual method, should I copy all the files into the same folder as my mfastboot.exe?

Globalrebel said:
I got it to show some info after running the command. Now, I have the following guide open . .
[GUIDE][VIDEO] Moto X - Return to 100% stock (using RSD Lite OR manual flash)
But I don't see anything in RSDLite after running it and clicking "Show Device"
Can I just to the manual method?
For manual method, should I copy all the files into the same folder as my mfastboot.exe?
Click to expand...
Click to collapse
Yes,I suggested manual method in last post. Faster and easier.
Yes extract the sbf to the folder containing mfastboot and fastboot.
The only thing you will do differently is one of the last lines that says carrier vzw, change it to carrier sprint.
Make sure u are using the 4.4.2 sprint sbf.
Good luck

samwathegreat said:
Yes,I suggested manual method in last post. Faster and easier.
Yes extract the sbf to the folder containing mfastboot and fastboot.
The only thing you will do differently is one of the last lines that says carrier vzw, change it to carrier sprint.
Make sure u are using the 4.4.2 sprint sbf.
Good luck
Click to expand...
Click to collapse
I am using Tmobile so I put tmo
But, after doing EVERYTHING, the phone reboots and I see it in PC, but screen is still not working?!?!?!
I did everything...
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
mfastboot flash system 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 oem config carrier tmo
fastboot oem fb_mode_clear
then
fastboot reboot
The phone boots and the phone is seen by my computer, but the screen is not working AT ALL
No water damage, and the phone was literally working perfectly fine 15 minutes ago. Just all of a sudden stopped showing the screen

Globalrebel said:
I am using Tmobile so I put tmo
But, after doing EVERYTHING, the phone reboots and I see it in PC, but screen is still not working?!?!?!
I did everything...
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
mfastboot flash system 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 oem config carrier tmo
fastboot oem fb_mode_clear
then
fastboot reboot
The phone boots and the phone is seen by my computer, but the screen is not working AT ALL
Click to expand...
Click to collapse
Bummer. You appear to have used the correct procedure.
This looks to be a hardware failure :/
Sorry, I don't have any further troubleshooting techniques for you...

Its all good. I think the screen just decided to die on me?!?! Which REALLY SUCKS! I'm still in my 1 year warranty policy. After fastbooting the original 4.4.2, will motorola know I did anything to the phone? IE, can they know I flashed anything?

Globalrebel said:
Its all good. I think the screen just decided to die on me?!?! Which REALLY SUCKS! I'm still in my 1 year warranty policy. After fastbooting the original 4.4.2, will motorola know I did anything to the phone? IE, can they know I flashed anything?
Click to expand...
Click to collapse
If you unlocked the bootloader they know it. Technically your warranty is void... But they might replace/fix it anyways. Don't mention it and see what happens. Let us know.

Related

[Q] Bootloop...Help?

So I rooted and unlocked yesterday, flashed cwm, and then flashed cm10 posted in the dev forum.
After having wifi issues, I decided to go to the Goldenrom.
Now I'm stuck in a boot loop. I can get back to recovery (and no, I forgot to make a backup), and tried wiping and flashing again. no luck.
I thought about trying to RSD but I can't. I can get to fastboot but RSD doesn't recognize it as being anything.
Please help.
Did you try holding the vol down and power until it shuts off. Then hold both vol down and up with power at the same time. It will give you options to choose. Then vol down to fastboot and press up to select it.
JayWheelz said:
Did you try holding the vol down and power until it shuts off. Then hold both vol down and up with power at the same time. It will give you options to choose. Then vol down to fastboot and press up to select it.
Click to expand...
Click to collapse
Yeah I've tried all that.
It can be mounted in fastboot, and RSD sees a device, but it doesn't have any information. Doesn't see it as an atrix, a razr, anything.
I also can't mount the sd card in cwm for file transfer. I was gonna try and flash one of the stock rooted roms I saw around here, but can't get the zip on storage.
Any thoughts?
rcloke91 said:
So I rooted and unlocked yesterday, flashed cwm, and then flashed cm10 posted in the dev forum.
After having wifi issues, I decided to go to the Goldenrom.
Now I'm stuck in a boot loop. I can get back to recovery (and no, I forgot to make a backup), and tried wiping and flashing again. no luck.
I thought about trying to RSD but I can't. I can get to fastboot but RSD doesn't recognize it as being anything.
Please help.
Click to expand...
Click to collapse
//////////////////////////////////////////////////////////////////////////////////////
you get in fastboot you in good shape....
rsd does not recognize your device.....uninstall mot helper drivers and install it back.....
you ll see now rsd recognize your device...
health unityni
htchd2fix said:
//////////////////////////////////////////////////////////////////////////////////////
you get in fastboot you in good shape....
rsd does not recognize your device.....uninstall mot helper drivers and install it back.....
you ll see now rsd recognize your device...
Click to expand...
Click to collapse
tried and rsd recognizes it, but doesn't say what it is.
uninstalled and reinstalled motohelper. didn't help anything, unfortunately. any other ideas, guys?
Don't worry
If you can get to fastboot don't worry your fine. Follow the steps below. You can just flash the stock files via fastboot tools.You can thank skeevy420 also. Got this from his post here.
http://forum.xda-developers.com/showthread.php?t=2226527
These are the steps:
Install Stock Fastboots JB
Download the respective fastboot zip you want to use
Extract the zip
Open a terminal to the extracted zips directory
Reboot into fastboot
Type the following commands in this order
fastboot flash boot boot.img
fastboot flash devtree device_tree.bin
fastboot erase system -w !
fastboot flash system system.img
fastboot -w
fastboot erase cache !
fastboot reboot
thanks
jkm43 said:
If you can get to fastboot don't worry your fine. Follow the steps below. You can just flash the stock files via fastboot tools.You can thank skeevy420 also. Got this from his post here.
http://forum.xda-developers.com/showthread.php?t=2226527
These are the steps:
Install Stock Fastboots JB
Download the respective fastboot zip you want to use
Extract the zip
Open a terminal to the extracted zips directory
Reboot into fastboot
Type the following commands in this order
fastboot flash boot boot.img
fastboot flash devtree device_tree.bin
fastboot erase system -w !
fastboot flash system system.img
fastboot -w
fastboot erase cache !
fastboot reboot
Click to expand...
Click to collapse
that did the trick. well done. im still curious as to what the problem was, but at least now i know it can be fixed.
So I did this and it worked, decided to re-root and reflash CM10.
I'm selling my Atrix now, so I've decided to reflash the stock rom. This time, though, the above steps didn't work. I'm stuck at the motorola logo. I can still get to fastboot. I've tried reflashing stock, but it hasn't worked, as I'm still stuck at the M logo.
I'd try the RSD Lite method, but even after reinstalling drivers, RSD doesn't recognize the device.
Any NEW thoughts?
I feel like a noob...
EDIT:
Nvm, figured it out. I forgot about the snapdragon fastboots...

[Q] xt1056 Sprint, wont connect to network please help

while attempting root on my sprint moto x using the moto x tool kit I decided hey the verizon root might work since theyre both cdma. bad idea. now every time i turn on my phone. com.android.phone force closes and it tells me sim card error. ive already flashed the stock image and I still get the error. any help would be greatly appreciated. thank you.
I attempted the slapmymoto method in the motoxtool kit and selected verizon
bradsinram said:
I attempted the slapmymoto method in the motoxtool kit and selected verizon
Click to expand...
Click to collapse
not sure what you did at all because all the phones are rooted the same way.
i would download the 4.2.2 firmware here
http://sbf.droid-developers.org/download.php?device=0&file=18
then go to this guide
http://forum.xda-developers.com/showthread.php?t=2603358
and follow the guide for returning to stock.
then after you are stock decide if you want to unlock your bootloader or not. then pick the guide based on what you decide and follow it for root
dray_jr said:
not sure what you did at all because all the phones are rooted the same way.
i would download the 4.2.2 firmware here
http://sbf.droid-developers.org/download.php?device=0&file=18
then go to this guide
http://forum.xda-developers.com/showthread.php?t=2603358
and follow the guide for returning to stock.
then after you are stock decide if you want to unlock your bootloader or not. then pick the guide based on what you decide and follow it for root
Click to expand...
Click to collapse
I've my device is 4.4 and ive already returned to stock and am still having the issue?
bradsinram said:
I've my device is 4.4 and ive already returned to stock and am still having the issue?
Click to expand...
Click to collapse
ok but if you did it threw the toolkit you might of still returned to the stock firmware for a different device
i restored completely to stock and am still having the same issue. please help
bradsinram said:
i restored completely to stock and am still having the same issue. please help
Click to expand...
Click to collapse
im going to bump this in hopes someone else takes a look.
can you look under settings/About phone/Status
what dose it way for
Network
signal strength
Mobile netowork type
also do you have a valid imei/meid please dont post this number here just check the number there with the number on the side of the box the phone came in
dray_jr said:
im going to bump this in hopes someone else takes a look.
can you look under settings/About phone/Status
what dose it way for
Network
signal strength
Mobile netowork type
also do you have a valid imei/meid please dont post this number here just check the number there with the number on the side of the box the phone came in
Click to expand...
Click to collapse
it says sprint for network then com.android.phone force closes. then it switches to searching for service. it say no signal strength and mobile network type is unknown. but it seriosuly force closes ever 2 seconds.
bradsinram said:
it says sprint for network then com.android.phone force closes. then it switches to searching for service. it say no signal strength and mobile network type is unknown. but it seriosuly force closes ever 2 seconds.
Click to expand...
Click to collapse
if it keeps force closing then you are not returning the phone to stock. because if you did that would not happen.
so i need you to explain to me what you are using when returning your phone to stock because it is not taking for some reason.
dray_jr said:
if it keeps force closing then you are not returning the phone to stock. because if you did that would not happen.
so i need you to explain to me what you are using when returning your phone to stock because it is not taking for some reason.
Click to expand...
Click to collapse
im using the 4.4 file that the motox toolkit downloads then i extract it to my adb folder and run these commands
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
mfastboot flash system system.img
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot reboot
everything appears to sucessfully flash
bradsinram said:
im using the 4.4 file that the motox toolkit downloads then i extract it to my adb folder and run these commands
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
mfastboot flash system system.img
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot reboot
everything appears to sucessfully flash
Click to expand...
Click to collapse
so what your now telling me 3-4 post later is that you did not listen to me at all so you asked for help and when i gave you the correct answer on what to do you did not listen.
so i will try this one more time the 4.4 firmware package you keep using from the Moto x toolkit is not the Sprint firmware so STOP using it and download the firmware from the link below. and flash it with the above commands like i told you to do in my first post
http://sbf.droid-developers.org/download.php?device=0&file=734
dray_jr said:
so what your now telling me 3-4 post later is that you did not listen to me at all so you asked for help and when i gave you the correct answer on what to do you did not listen.
so i will try this one more time the 4.4 firmware package you keep using from the Moto x toolkit is not the Sprint firmware so STOP using it and download the firmware from the link below. and flash it with the above commands like i told you to do in my first post
http://sbf.droid-developers.org/download.php?device=0&file=734
Click to expand...
Click to collapse
okay I will do. so i just find it weird they have an almost identical name and both say sprint. but thank you and im download the one you provided now.
dray_jr said:
so what your now telling me 3-4 post later is that you did not listen to me at all so you asked for help and when i gave you the correct answer on what to do you did not listen.
so i will try this one more time the 4.4 firmware package you keep using from the Moto x toolkit is not the Sprint firmware so STOP using it and download the firmware from the link below. and flash it with the above commands like i told you to do in my first post
http://sbf.droid-developers.org/download.php?device=0&file=734
Click to expand...
Click to collapse
so ive used the file you provided me with and am still having the same exact issues. I appreciate your help.
I feel like i need to rewrite the radio partition but which I'm assumung is the NON-HLOS but every time i try to write to it i get permission denied
ok sorry i left out a command i think i know what is going on
Code:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
mfastboot flash system system.img
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase userdata
fastboot erase cache
fastboot reboot
i know you just did this but do it one more time and make sure you do the erase userdata and cache commands and then reboot.
after wiping everything i am not sure what would be wrong i have a sprint device and i have never had this issue.
dray_jr said:
ok sorry i left out a command i think i know what is going on
Code:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
mfastboot flash system system.img
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase userdata
fastboot erase cache
fastboot reboot
i know you just did this but do it one more time and make sure you do the erase userdata and cache commands and then reboot.
after wiping everything i am not sure what would be wrong i have a sprint device and i have never had this issue.
Click to expand...
Click to collapse
yeah I've tried it about ten times now and i think theres something else from the verizon root that mustve gotten flashed and is causing this
Well you have to flash the NON-HLOS.bin or it is not going to work.
Why not just download the full Sprint firmware file(I believe you've already done this) download rsdlite, remove the var line from the xml, and with one click your phone will work fine again.
Steve-x said:
Well you have to flash the NON-HLOS.bin or it is not going to work.
Why not just download the full Sprint firmware file(I believe you've already done this) download rsdlite, remove the var line from the xml, and with one click your phone will work fine again.
Click to expand...
Click to collapse
Thank you so much! I was wondering what kept causing rsd lite to fail. Im lead technician at a spring store and could just AE it but really dont want a refurb, especially since this phone is two days old
sorry but how do I remove the var line?
ive got it figured out thank you for your help

[Q] Attempted to Downgrade and now bricked [solved]

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!

Phone not booting after OTA

So today I got an update for a new firmware, it was a small 125 mb patch, no big deal. I downloaded it and installed it a couple of hours later, I leave it to install and when I'm back my phone is frozen on the Motorola logo and the "Powered by android" text written below, but it won't get past that. I left it for almost an hour and it won't boot, I tried forcing a reboot and it gets me back to the same screen.
Is there any way I could fix it, preferably while keeping my data? Especially the what's app gallery.
Thanks a lot guys, I'm kinda panicking here.
Ps. I'm not rooted, everything is completely stock.
it's Stuck on Moto Boto logo ?
Yes. I tried doing a factory reset and that doesn't work either, it sends me right back to the boot logo.
Sorry to not have any solutions but my girlfriends phone has probably had the exact same thing happen. At about 10PM tonight she got an update notification and told it to install. almost two hours later she checked the phone again to see it stuck on the boot logo and incredibly hot. She restarted it and same thing, stuck on the boot logo. Same as you, completely stock phone. Never been modified in anyway.
I had her go into recovery and wipe cache, no change at all. I've now had her do a factory reset twice as some similar problems mentioned that as a solution. No change, still just gets stuck on the boot screen.
My assumption at this point is that this update has completely trashed the phone and it's completely unrecoverable on the device at least.
I'm willing to learn how to install a new rom from scratch if that would help, preferably a stock one. The problem is that Motorola doesn't have any stores where I live, I ordered my phone off amazon.
So is there any method to fix it? You can instruct me if you could or at least tell me what to look for on google.
Thanks a lot man.
darthlawl said:
I'm willing to learn how to install a new rom from scratch if that would help, preferably a stock one. The problem is that Motorola doesn't have any stores where I live, I ordered my phone off amazon.
So is there any method to fix it? You can instruct me if you could or at least tell me what to look for on google.
Thanks a lot man.
Click to expand...
Click to collapse
I didn't think that you have any way to install urself stock without voiding warranty so u have 2 choices u can go for service or unlock and install any rom u want
vaisakmct said:
I didn't think that you have any way to install urself stock without voiding warranty so u have 2 choices u can go for service or unlock and install any rom u want
Click to expand...
Click to collapse
My warranty is already over, I just want stock because I like it.
Are you sure a rom installation would work?
Ps. I can't unlock the bootloader since I can't access the OS
Unlock boot loader does not acess to os it is simple
---------- Post added at 01:25 AM ---------- Previous post was at 01:23 AM ----------
Just go to fastboot mode and unlocking can done from pc and install twrp then u can flash roms
vaisakmct said:
Unlock boot loader does not acess to os it is simple
---------- Post added at 01:25 AM ---------- Previous post was at 01:23 AM ----------
Just go to fastboot mode and unlocking can done from pc and install twrp then u can flash roms
Click to expand...
Click to collapse
What do you mean?
I'm a total beginner when it comes to android, I'm more of a windows guy. Can you walk me through the steps?
It´s not that easy to guide someone through all the steps. First thing you have to do is unlock your bootloader,described here: http://forum.xda-developers.com/moto-g-2014/general/wip-unlock-bootloader-moto-g-2nd-gen-t2875728. Read all the steps,it´s not that difficult.
You need all the drivers,by motorola and android, linked in the tutorial. I recomend Minimal ADB and Fastboot instead of Android SDK, it´s easier. Install it in the root of your windows partition,like C:\Minimal ADB and Fastboot. So if you open a command prompt the path is short and you know it.
After the unlock process you´ll need to flash a custom recovery, you can read how to do that here: http://forum.xda-developers.com/moto-g-2014/general/xt1063-t3018818.
There´s a part called Flashing TWRP Recovery . You don´t need to do that with Flashify (you surely can if you want but I think this way is easier to do), just download the custom recovery TWRP from here: https://dl.twrp.me/titan/.
Place the .img file in the Minimal ADB and Fastboot folder and connect the phone to the PC. After that you open a command prompt again from the Minmal ADB and fastboot folder (open the folder and hold Shift and right click and press "open command window here".
Now type the command
Code:
adb reboot bootloader
When the phone has booted to bootloader type
Code:
fastboot devices
A string of numbers should appear,that means your phone is connected.
Now type
fastboot flash recovery "name of the downloaded TWRP .img file", in your case that should be
Code:
fastboot flash recovery twrp-2.8.6.0-titan.img
Now everytime when you boot to recovery you´ll see a menu with a lot of features like install,wipe,backup,restore etc.
From here you can flash any rom you like, a stock rom, a stock based rom or any other like cyanogen or AOSP.
If you want to flash stock again you´ll need to know the name of your firmware,it differs from country and version. You can search for it here: http://forum.xda-developers.com/moto-g-2014/development/original-motorola-firmware-collection-t3153533.
It´s late now here, if you are at this point and have decided what rom to flash post again or pm me.
I hope my exclamation is understandable and I´ve made no faults, everyone else please correct me then!
Wolfcity said:
It´s not that easy to guide someone through all the steps. First thing you have to do is unlock your bootloader,described here: http://forum.xda-developers.com/moto-g-2014/general/wip-unlock-bootloader-moto-g-2nd-gen-t2875728. Read all the steps,it´s not that difficult.
You need all the drivers,by motorola and android, linked in the tutorial. I recomend Minimal ADB and Fastboot instead of Android SDK, it´s easier. Install it in the root of your windows partition,like C:\Minimal ADB and Fastboot. So if you open a command prompt the path is short and you know it.
After the unlock process you´ll need to flash a custom recovery, you can read how to do that here: http://forum.xda-developers.com/moto-g-2014/general/xt1063-t3018818.
There´s a part called Flashing TWRP Recovery . You don´t need to do that with Flashify (you surely can if you want but I think this way is easier to do), just download the custom recovery TWRP from here: https://dl.twrp.me/titan/.
Place the .img file in the Minimal ADB and Fastboot folder and connect the phone to the PC. After that you open a command prompt again from the Minmal ADB and fastboot folder (open the folder and hold Shift and right click and press "open command window here".
Now type the command
Code:
adb reboot bootloader
When the phone has booted to bootloader type
Code:
fastboot devices
A string of numbers should appear,that means your phone is connected.
Now type
fastboot flash recovery "name of the downloaded TWRP .img file", in your case that should be
Code:
fastboot flash recovery twrp-2.8.6.0-titan.img
Now everytime when you boot to recovery you´ll see a menu with a lot of features like install,wipe,backup,restore etc.
From here you can flash any rom you like, a stock rom, a stock based rom or any other like cyanogen or AOSP.
If you want to flash stock again you´ll need to know the name of your firmware,it differs from country and version. You can search for it here: http://forum.xda-developers.com/mot...riginal-motorola-firmware-collection-t3153533.
It´s late now here, if you are at this point and have decided what rom to flash post again or pm me.
I hope my exclamation is understandable and I´ve made no faults, everyone else please correct me then!
Click to expand...
Click to collapse
Its good guide follow these steps
If you want to go stock, I recommend you to go with the mfastboot method . . .
because it doesn't even need unlocked bootloader or any recovery,
The following link is having a mfastboot folder, in which, Moto G 2014(XT1068) stock 5.0.2 factory firmware is stored and, you just have to extract the folder and open it then pressing & holding shift + RMB and select "Open Command Window Here".
(Now press Power + Volume Down simultaneously, and you should go to the bootloader mode, if you don't know that )
Now in the command window, check your phone is connected with USB and type below code and press Enter.
Code:
fastboot devices
if any code(like for eg. ZDMJK2312) is shown, you're connected,
if not, try reconnecting the USB and try again.
Once properly connected, now you can flash the follwing commands one by one, to get your device to life.
Code:
Moto G 2014 Stock 5.0.2 Restore Script
------------------------------------------------------------------|
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 system system.img_sparsechunk.4
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
mfastboot.exe reboot
------------------------------------------------------------------|
BTW this happened to me 6 months back and the same helped me.
mfastboot
Note : The above method is for only the model XT1068, because the firmware in the folder is for that model only, so plz make sure your model before proceeding.
And plz follow each and every step properly.
Thanks . . .
Alright thanks people! I'll try ArtRahul's method since it's easier and i was quite satisfied with stock. If that doesn't work I'll try Wolfcity's method.
Alright, so this is an update. ArtRahul's method works great and it's really easy. If anyone looks for a solution and finds this thread, just make sure you find the exact model of your phone and google the firmware. Here's where I found mine
http://www.droidviews.com/restore-moto-g-2014-to-stock-and-lock-the-bootloader/
It has links to other versions too. Good luck!
darthlawl said:
What do you mean?
Click to expand...
Click to collapse
if ur phone is going to fastboot mode u can install twrp, no os is needed for doing this
darthlawl said:
Ps. I can't unlock the bootloader since I can't access the OS
Click to expand...
Click to collapse
darthlawl said:
What do you mean?
Click to expand...
Click to collapse
you don't have to access to os in order to unlock the bootloader, go to android development section on this forum for moto g 2014 & follow any thread that guides about unlocking bootloader.
darthlawl said:
Alright, so this is an update. ArtRahul's method works great and it's really easy. If anyone looks for a solution and finds this thread, just make sure you find the exact model of your phone and google the firmware. Here's where I found mine
http://www.droidviews.com/restore-moto-g-2014-to-stock-and-lock-the-bootloader/
It has links to other versions too. Good luck!
Click to expand...
Click to collapse
did anything work?
my moto g2 was rooted .i got notification that update 5.1.1 is available .but after update it is stuck in bootloop::crying:
---------- Post added at 03:17 AM ---------- Previous post was at 03:03 AM ----------
it is giving me failed to validate system image error after first command mfastboot.exe oem lock begin

Turbo firmware?

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.

Categories

Resources