I have a unlocked bootloader US Moto X 2014 Pure Edition with stock recovery and currently non-rooted. No modifications to the system that I am aware of (NO XPOSED, ETC).
I went into SuperSu and did the complete unroot and rebooted and then tried to take the OTA and it was unsuccessful, as I figured it would be.
I am running System Version 22.21.11 victara_tmo.tmo.en.us and Build LXE22.46.11.
My question is this: I have requested the download for the 5.0 factory image from Motorola's website. Can I download it and then flash it with a similar process like I do with my Nexus 5 where I flash system, boot, bootloader, and radio and then take the 5.1 OTA? My goal is not to lose data or apps.
If I follow the commands on Motorola's website, am I going to lose data and apps? The commands would be:
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot reboot-bootloader
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot reboot
Did you also uninstall BusyBox? I did the same thing last night, stock recovery, rooted with BusyBox, unrooted through SuperSu and uninstalled BusyBox, the OTA update worked perfectly and I just re-rooted with CF-Auto, good to go.
As far as flashing the factory image, as long as you don't flash cache.img or userdata.img you should keep all of your data, I just used the same method on my Nexus 9.
inertiamonster said:
Did you also uninstall BusyBox? I did the same thing last night, stock recovery, rooted with BusyBox, unrooted through SuperSu and uninstalled BusyBox, the OTA update worked perfectly and I just re-rooted with CF-Auto, good to go.
As far as flashing the factory image, as long as you don't flash cache.img or userdata.img you should keep all of your data, I just used the same method on my Nexus 9.
Click to expand...
Click to collapse
Thanks I'll try that! As far as flashing, I just follow Motorola's steps minus flashing cache.img and userdata.img and I should be fine right?
I also forgot to mention to make sure if the factory image comes with a flashing script be sure to check that it doesn't have a wipe command!!
Yes, since their method does not appear to use a script (based on what you pasted in the OP) you don't need to worry about it sending a wipe command or flashing images you don't want it to, just follow the manual flashing steps minus those two imgs if present.
I unrooted through Super Su and uninstalled BusyBox and it did not work. I guess I'll have to flash and then take the OTA to 5.1 when I get permission to download the factory image Maybe my root method was different from yours. I don't know.
Hmm, strange. Did you use CF-Auto to root? You rebooted after unrooting and removing BusyBox?
I honestly don't remember what I used to root. I'll reboot and try again and let you know what happens.
No success. Will try to flash 5.0 and then upgrade via OTA to 5.1.
inertiamonster said:
I did the same thing last night, stock recovery, rooted with BusyBox, unrooted through SuperSu and uninstalled BusyBox, the OTA update worked perfectly and I just re-rooted with CF-Auto, good to go.
Click to expand...
Click to collapse
Which one should I do first, unroot SuperSu or uninstall BusyBox? Do I need to reboot between those two steps?
Matthewlawson3 said:
No success. Will try to flash 5.0 and then upgrade via OTA to 5.1.
Click to expand...
Click to collapse
I may have a problem. I made a mistake in the flashing sequence and accidently booted instead of flashed the boot.img. So I reloaded into the bootloader and continued the flashing and now when I rebooted it goes to the logo and then turns off. Help me!
I reluctantly erased userdata and cache and got it to work again. However, when I booted up it was 4.4.4, how is that possible? I requested the right file.
Matthewlawson3 said:
I reluctantly erased userdata and cache and got it to work again. However, when I booted up it was 4.4.4, how is that possible? I requested the right file.
Click to expand...
Click to collapse
Not possible. You requested the wrong file.
Download 5.0 from here:
http://www.graffixnyc.com/motox.php
Sent from my XT1095 using Tapatalk
AGISCI said:
Not possible. You requested the wrong file.
Download 5.0 from here:
http://www.graffixnyc.com/motox.php
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
Thank you. I went ahead and just erased everything and upgraded to 5.0 by OTA then to 5.1 by OTA, but thanks again. I appreciate it.
onmyouji said:
Which one should I do first, unroot SuperSu or uninstall BusyBox? Do I need to reboot between those two steps?
Click to expand...
Click to collapse
I removed BB and then unrooted and rebooted, not sure if the order matters but rebooting is a good idea to make sure root is gone.
Related
I thought I prevented my phone from downloading the OTA to 4.4.3 on my Dev Edition Unlocked bootloader running 4.4.2 and TWRP. I obviously did not and now my phone keeps rebooting into TWRP.
Is there a way to stop this and clear it out somehow?
reno55 said:
I thought I prevented my phone from downloading the OTA to 4.4.3 on my Dev Edition Unlocked bootloader running 4.4.2 and TWRP. I obviously did not and now my phone keeps rebooting into TWRP.
Is there a way to stop this and clear it out somehow?
Click to expand...
Click to collapse
Try using Titanium Backup to freeze MotorolaOTA
samwathegreat said:
Try using Titanium Backup to freeze MotorolaOTA
Click to expand...
Click to collapse
Actually I think I can fix by flashing stock recovery but where can I find the stock recovery image?
reno55 said:
Actually I think I can fix by flashing stock recovery but where can I find the stock recovery image?
Click to expand...
Click to collapse
YES, you can fix by flashing stock recovery assuming you haven't heavily modified your system. Flashing the stock recovery will make the phone try to flash the OTA.
You'll need to download the SBF for your phone here: http://sbf.droid-developers.org/phone.php?device=0
Unzip the file. I'm assuming you already have the fastboot and mfastboot binaries as well as the android SDK.
Place the file "recovery.img" in the same folder as mfastboot & fastboot. Make sure USB Debugging is enabled (or manually boot into bootloader).
Type mfastboot flash recovery recovery.img
Done.
Good Luck
samwathegreat said:
YES, you can fix by flashing stock recovery assuming you haven't heavily modified your system. Flashing the stock recovery will make the phone try to flash the OTA.
You'll need to download the SBF for your phone here: http://sbf.droid-developers.org/phone.php?device=0
Unzip the file. I'm assuming you already have the fastboot and mfastboot binaries as well as the android SDK.
Place the file "recovery.img" in the same folder as mfastboot & fastboot. Make sure USB Debugging is enabled (or manually boot into bootloader).
Type mfastboot flash recovery recovery.img
Done.
Good Luck
Click to expand...
Click to collapse
I think I just did this correctly.......it is on Android is upgrading now.....
I can just flash a custom recovery now right?
reno55 said:
I think I just did this correctly.......it is on Android is upgrading now.....
I can just flash a custom recovery now right?
Click to expand...
Click to collapse
If the upgrade is successful, absolutely.
mfastboot flash recovery twrp-2.6.3.1-ghost-4.4.img
download twrp from here: http://forum.xda-developers.com/moto-x/development/recovery-unlocked-twrp-2-6-3-1-android-t2534850
samwathegreat said:
If the upgrade is successful, absolutely.
mfastboot flash recovery twrp-2.6.3.1-ghost-4.4.img
download twrp from here: http://forum.xda-developers.com/moto-x/development/recovery-unlocked-twrp-2-6-3-1-android-t2534850
Click to expand...
Click to collapse
Can I flash philz?
reno55 said:
Can I flash philz?
Click to expand...
Click to collapse
Don't see why not. Just substitute the filename for philz recovery instead.
Get Philz here: http://forum.xda-developers.com/moto-x/development/xt10xx-philz-touch-t2612149
I have not used Philz personally...I prefer TWRP, but it looks like (unlike TWRP), that there is a different img for each variant of the Moto X. You will need to be careful to download the correct one.
I got the XT1053 T-Mobile version, rooted, unlocked with titanium backup, TWRP and Xposed. I just got the software update notice and I am currently trying to decide if I want to update or not. Correct me if I am wrong, but from what I have read, if I want to get the OTA, is the best way to flash the SBF and update to 4.4.3 and then configure the phone again? Is there no way to complete the OTA without flashing a stock recovery? Is it worth it? I love this phone, but there are no custom ROM's that are stock based for XT1053 which would be ideal since I don't want to lose all the extra goodies of the stock ROM.
frankie_p said:
I got the XT1053 T-Mobile version, rooted, unlocked with titanium backup and Xposed. I just got the software update notice and I am currently trying to decide if I want to update or not. Correct me if I am wrong, but from what I have read, if I want to get the OTA, is the best way to flash the SBF and update to 4.4.3 and then configure the phone again? Is it worth it? I love this phone, but there are no custom ROM's that are stock based for XT1053 which would be ideal since I don't want to lose all the extra goodies of the stock ROM.
Click to expand...
Click to collapse
Ugh! I am having all kinds of issues with 4.4.3. There is not a way to go back to 4.4.2 is there?
frankie_p said:
I got the XT1053 T-Mobile version, rooted, unlocked with titanium backup and Xposed. I just got the software update notice and I am currently trying to decide if I want to update or not. Correct me if I am wrong, but from what I have read, if I want to get the OTA, is the best way to flash the SBF and update to 4.4.3 and then configure the phone again? Is it worth it? I love this phone, but there are no custom ROM's that are stock based for XT1053 which would be ideal since I don't want to lose all the extra goodies of the stock ROM.
Click to expand...
Click to collapse
YES, that is the best way to do it. You can -try- disabling xposed, and un-doing any major modifications you have done (like freezing or removing any system apps). You want it to be as close to stock as possible before you try to accept the OTA, which includes flashing back the stock recovery.
SBFing back to stock 4.4.2 FIRST, and accepting the update, THEN flashing TWRP and rooting, then re-configuring everything and installing your apps is MUCH safer and pretty much guarantees that your filesystem will be 100% intact.
If it were ME, I would SBF first -- for whatever that's worth...
Good Luck
---------- Post added at 11:04 PM ---------- Previous post was at 11:01 PM ----------
reno55 said:
Ugh! I am having all kinds of issues with 4.4.3. There is not a way to go back to 4.4.2 is there?
Click to expand...
Click to collapse
Sure. It's just slightly more complicated. You'll need the entire 4.4.2 SBF for your carrier.
Do this: Reboot to bootloader
FIRST, JUST flash gpt.bin and motoboot.img:
fastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
Now you need to REBOOT back into bootloader (to prevent gpt.bin mis-match -- if you don't reboot here, you will get errors). Do this by typing:
mfastboot reboot-bootloader
Now flash the rest of the files:
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
Reboot, and you should be back to stock 4.4.2
And finally the disclaimer: DO NOT TRY TO DOWNGRADE TO ANY VERSION PRIOR TO 4.4.2 .....if you don't want a brick.
It's ok to downgrade 4.4.3 to 4.4.2 because the bootloader version did not change. It is NOT safe to downgrade to anything prior (4.4 or 4.2.2).
I totally forgot I was rooted and had TWRP and I took the OTA update.
Now the phone is in an infinite loop of rebooting.
What do I need to do to remedy this?
Thank you
Same phone, same problem but I was using clockwork mod recovery. You need to flash the stock recovery using Factbook, then the other update will take.
There are some existing threads that will fill you in with the details!
Good luck.
Sent from my Nexus 7 using Tapatalk
There are PLENTY of threads saying you can NOT install the OTA while you have a custom recovery like TWRP or CWM installed. Doing so causes a boot loop. Almost every one of those posts (at least the ones I've made) says if you get into this situation you need to erase your cache to get out of the boot loop
Boot the phone into fastboot/bootloader mode. Then use mfastboot on the PC to erase your cache. Return to stock and try again.
If you are close enough to stock, you can just try to boot the phone into mfastboot mode, flash STOCK recovery, and see if you can install the OTA, or if it will fail (due to varying too much from stock).
this sticky was helpful
MFastboot(Used for manually downgrading to 4.2.2)
MFastboot
For firmware Download pick what firmware you want from the link below... make sure its the one you have. you cannot downgrade
http://sbf.droid-developers.org/phone.php?device=0
reboot to the bootloader
i used only part of the code from the sticky
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 flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
i was then able to then flash OTA whilst keeping the bootloader unlocked, kept root, kept all my files and settings intact.
Ditto. I just downloaded the pre update firmware and extracted the recovery.IMG file and flashed it with flashify uninstalled xposed framework and boom three reboots and the update is done . reinstall xposed framework and all my settings are still there . VZW Dev edition. Didn't even lose root.
Sent from my XT1060 using Tapatalk
That's how it's done simple and effective.
I did that code line that jadeddjay posted but only did the step through the recovery.img. I then rebooted and it worked perfectly and installed the OTA. I then went back into fastboot and installed TWRP and am rooted again.
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!
So I am on stock Android 5.1. Had rooted earlier but un rooted. Just got a 4.6 MB update. The update installed properly but my device will not boot. It reaches the boot logo and then I see a black screen. What steps should I be taking now?
P.s It wont boot into recovery, nor is it charging.
Can you get into fastboot mode?
Sent from my XT1095 using Tapatalk
AGISCI said:
Can you get into fastboot mode?
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
Is that by holding power and volume down button?
If yes then I just got there..
Should I be flashing stock 5.1 again?
AGISCI said:
Can you get into fastboot mode?
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
Or should I be following these steps?
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
Yes that is fastboot. As long as you have that your phone is salvageable.
What model do you have? xt1092, 1093, 1095, etc?
To use fastboot you need the android program called fastboot. If you go to the android website you can install it by downloading and installing the android sdk.
You have 2 options and please pay attention so as to not brick your phone.
You can try to factory reset, it may fix the phone but it erases all of your data. To do this type:
fastboot erase userdata
fastboot erase cache
fastboot rebooot
The other option is to flash the full factory image. I need to know your model before I can get you the correct factory image.
Please be aware that right now the new factory image that has this small update does not exist. So you will have to downgrade to the 5.1 without this patch you installed. However do NOT install the OTA patch!!! After a downgrade using an OTA can permanently brick your phone. You will have to wait till the full firmware is released that has this patch then you will be able to safely upgrade.
Sent from my XT1095 using Tapatalk
AGISCI said:
Yes that is fastboot. As long as you have that your phone is salvageable.
What model do you have? xt1092, 1093, 1095, etc?
To use fastboot you need the android program called fastboot. If you go to the android website you can install it by downloading and installing the android sdk.
I also have fastboot installed as I had rooted my device earlier and unrooted completely.
You have 2 options and please pay attention so as to not brick your phone.
You can try to factory reset, it may fix the phone but it erases all of your data. To do this type:
fastboot erase userdata
fastboot erase cache
fastboot rebooot
The other option is to flash the full factory image. I need to know your model before I can get you the correct factory image.
Please be aware that right now the new factory image that has this small update does not exist. So you will have to downgrade to the 5.1 without this patch you installed. However do NOT install the OTA patch!!! After a downgrade using an OTA can permanently brick your phone. You will have to wait till the full firmware is released that has this patch then you will be able to safely upgrade.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
I have a XT 1095. I have the factory image TMO_Pure_5.1_LPE23.32-21.3_5_23.16.3.victara_tmo.tmo.en.US.tgz from the motorola website. Hypothetically speaking if I do a factory reset I can take the OTA as I dont mind losing any data on the phone. All my photos are backed up to google drive so it is not an issue for me.
Also I have fastboot on my laptop as I had rooted my phone and then unrooted it completely.
If you do a factory reset you will not need to take an OTA because it is already installed. All a factory reset does is erase the cache and your data, it does not downgrade nor uninstall an OTA.
Sent from my XT1095 using Tapatalk
AGISCI said:
If you do a factory reset you will not need to take an OTA because it is already installed. All a factory reset does is erase the cache and your data, it does not downgrade nor uninstall an OTA.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
So if I factory reset I can take any further OTAs that release without any worries right?
Yes. OTA is only dangerous if you downgrade. A factory reset is not a downgrade. However if the factory reset does not work to fix your problem, then the other option I mentioned of downgrading will be your only option. That firmware file you have from motorola IS a downgrade because it does not have the patch you installed in it. Which means you would have to wait for the new firmware file to be released before you can patch your phone with the latest version. So if you flash that file you have don't upgrade via OTA.
Sent from my XT1095 using Tapatalk
AGISCI said:
Yes. OTA is only dangerous if you downgrade. A factory reset is not a downgrade. However if the factory reset does not work to fix your problem, then the other option I mentioned of downgrading will be your only option. That firmware file you have from motorola IS a downgrade because it does not have the patch you installed in it. Which means you would have to wait for the new firmware file to be released before you can patch your phone with the latest version.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
Okay. I shall factory reset and revert. Thanks a ton for the info!
Only revert if factory reset does not work.
Sent from my XT1095 using Tapatalk
AGISCI said:
Yes. OTA is only dangerous if you downgrade. A factory reset is not a downgrade. However if the factory reset does not work to fix your problem, then the other option I mentioned of downgrading will be your only option. That firmware file you have from motorola IS a downgrade because it does not have the patch you installed in it. Which means you would have to wait for the new firmware file to be released before you can patch your phone with the latest version. So if you flash that file you have don't upgrade via OTA.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
So it turns out my phone will not boot even after factory reset via the fastboot method. Comes to the boot logo and switches off.
pulley06 said:
Okay. I shall factory reset and revert. Thanks a ton for the info!
Click to expand...
Click to collapse
Sorry to hijack your thread, but I'm having the same issue. (Shows Unlocked Bootloader screen, then briefly shows Moto logo, boot animation, then blackscreen). I can access fastboot (Power + Vol Up + Vol Down) as well.
Once you're able to try factory resetting, could you post if that solves the problem?
At the moment I'm waiting for permission to access the latest Motorola factory image. Is there another source for these that anyone knows of?
Thanks!
Edit: Your post squeezed in before mine!
malerick003 said:
Sorry to hijack your thread, but I'm having the same issue. (Shows Unlocked Bootloader screen, then briefly shows Moto logo, boot animation, then blackscreen). I can access fastboot (Power + Vol Up + Vol Down) as well.
Once you're able to try factory resetting, could you post if that solves the problem?
At the moment I'm waiting for permission to access the latest Motorola factory image. Is there another source for these that anyone knows of?
Thanks!
Edit: Your post squeezed in before mine!
Click to expand...
Click to collapse
Factory reset does not allow me to boot. It is so surprising :/
So now I have to wait for them to release the factory images to be able to take OTA? And I should not be taking any OTA after flashing this stock file?
AGISCI said:
Only revert if factory reset does not work.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
It isnt
pulley06 said:
Factory reset does not allow me to boot. It is so surprising :/
So now I have to wait for them to release the factory images to be able to take OTA? And I should not be taking any OTA after flashing this stock file?
Click to expand...
Click to collapse
I requested the most recent stock image from Motorola. (Can't link directly: motorola-global-portal.custhelp DOT com/app/standalone/bootloader/recovery-images) Needs to be approved apparently...
My understanding is that this does not contain the recent patch (that is causing our bootloop). Based on what AGISCI is saying, taking the OTA after flashing the factory images is bad news...
I'm guessing that flashing the updated factory images (over these older versions) when they are released will make everything okay?
Pulley:
Use these commands to downgrade the firmware:
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
But do NOT take the OTA. You will have to wait for motorola to post a new full firmware before you can upgrade.
Malerick:
Your problem is not the same. His phone does not boot. Yours does.
Your problem is known as the black screen. It can be easily fixed with a factory reset.
Sent from my XT1095 using Tapatalk
malerick003 said:
I requested the most recent stock image from Motorola. (Can't link directly: motorola-global-portal.custhelp DOT com/app/standalone/bootloader/recovery-images) Needs to be approved apparently...
My understanding is that this does not contain the recent patch (that is causing our bootloop). Based on what AGISCI is saying, taking the OTA after flashing the factory images is bad news...
I'm guessing that flashing the updated factory images (over these older versions) when they are released will make everything okay?
Click to expand...
Click to collapse
Yeah I think that is my assumption as well :/ Will have to wait for AGISCI to give his inputs on that. I have access to that file. I can upload it on my dropbox if u want it right now.
AGISCI said:
Pulley:
Use these commands to downgrade the firmware:
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
But do NOT take the OTA. You will have to wait for motorola to post a new full firmware before you can upgrade.
Malerick:
Your problem is not the same. His phone does not boot. Yours does.
Your problem is known as the black screen. It can be easily fixed with a factory reset.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
From what I understand my problem and his seem to be the same to me. Even I have a black screen after the moto boot logo and it does not boot. Isnt that the same Malerick is having right?
I installed CM13 on my phone because I wanted early access to Marshmellow, it was all good until the first reboot. Now I am constantly spammed with "com.android.phone has been stopped" or similar, with OK greyed out. After 5 minutes of waiting, the messages disappeared but the phone was incredibly laggy, like, changing the home page took about 10 seconds. I have tried,
Dalvik Wipe
Reflashing
Reflashing older nightlies
Using the Cyanogen recovery rather than TWRP(I heared TWRP had radio issues)
Taking sim in/out while phone running to see if it detects it
Not flashing OpenGapps to see if it made a difference
I know marshmellow is being rolled out right now, but I have retgb and no ota has appeared, I would also like to know the requirements for this to do so, e.g locking bootloader.
Cheers c:
progamer123420666 said:
I installed CM13 on my phone because I wanted early access to Marshmellow, it was all good until the first reboot. Now I am constantly spammed with "com.android.phone has been stopped" or similar, with OK greyed out. After 5 minutes of waiting, the messages disappeared but the phone was incredibly laggy, like, changing the home page took about 10 seconds. I have tried,
Dalvik Wipe
Reflashing
Reflashing older nightlies
Using the Cyanogen recovery rather than TWRP(I heared TWRP had radio issues)
Taking sim in/out while phone running to see if it detects it
Not flashing OpenGapps to see if it made a difference
I know marshmellow is being rolled out right now, but I have retgb and no ota has appeared, I would also like to know the requirements for this to do so, e.g locking bootloader.
Cheers c:
Click to expand...
Click to collapse
You didn't tryed to wipe /data ? (making a backup before ofc)
Have the latest twrp ? currently is 3.0.0-1
You can flash retEU on you retGB phone ( just don't relock the bootloader, never relock unless you know what are you doing )
You have an XT1072 ? If yes this is all you need to flash back stock mm
XT1072 MM MEGA Mirror 1
XT1072 MM MEGA Mirror 2
Fastboot+mfastbootv2
MM BAT File
Put everything in the same folder and launch the bat file as admin to flash the phone, first boot is SLOW on mm, very slow, so don't panic.
dr.nic said:
You didn't tryed to wipe /data ? (making a backup before ofc)
Have the latest twrp ? currently is 3.0.0-1
You can flash retEU on you retGB phone ( just don't relock the bootloader, never relock unless you know what are you doing )
You have an XT1072 ? If yes this is all you need to flash back stock mm
XT1072 MM MEGA Mirror 1
XT1072 MM MEGA Mirror 2
Fastboot+mfastbootv2
MM BAT File
Put everything in the same folder and launch the bat file as admin to flash the phone, first boot is SLOW on mm, very slow, so don't panic.
Click to expand...
Click to collapse
So I wipe data, cache and system, then flash mm, and boot, then reboot after its set up? Will I receive retgb updates in the future?
progamer123420666 said:
So I wipe data, cache and system, then flash mm, and boot, then reboot after its set up?
Click to expand...
Click to collapse
No i suggested to try a /data wipe first to check if was that one since you didn't listed that, to flash stock MM just reboot to bootloader, connect the usb cable and launch the bat file.
progamer123420666 said:
Will I receive retgb updates in the future?
Click to expand...
Click to collapse
No, you can't receive OTAs if you have bootloader unlocked or a modified /system (ex. root).
If everything is fine for OTAs you will receive the eu one.
To go back to GB stock use this rom http://www.filefactory.com/file/42o...B22.99-24.12_cid7_subsidy-DEFAULT_CFC.xml.zip
and use this to flash it, that bat file work only for MM, LL have 5 system.img chunks.
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash 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
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
Click to expand...
Click to collapse
dr.nic said:
You didn't tryed to wipe /data ? (making a backup before ofc)
Have the latest twrp ? currently is 3.0.0-1
You can flash retEU on you retGB phone ( just don't relock the bootloader, never relock unless you know what are you doing )
You have an XT1072 ? If yes this is all you need to flash back stock mm
XT1072 MM MEGA Mirror 1
XT1072 MM MEGA Mirror 2
Fastboot+mfastbootv2
MM BAT File
Put everything in the same folder and launch the bat file as admin to flash the phone, first boot is SLOW on mm, very slow, so don't panic.
Click to expand...
Click to collapse
dr.nic said:
No i suggested to try a /data wipe first to check if was that one since you didn't listed that, to flash stock MM just reboot to bootloader, connect the usb cable and launch the bat file.
No, you can't receive OTAs if you have bootloader unlocked or a modified /system (ex. root).
If everything is fine for OTAs you will receive the eu one.
To go back to GB stock use this rom http://www.filefactory.com/file/42o...B22.99-24.12_cid7_subsidy-DEFAULT_CFC.xml.zip
and use this to flash it, that bat file work only for MM, LL have 5 system.img chunks.
Click to expand...
Click to collapse
Alright, cheers