I received the Marshmallow OTA on my phone today, and searching about it made me concerned about some things, in special Bluetooth and battery life; the first because I use Bluetooth to connect to my stereo, the latter because this phone can get over 12 hours of Screen-on Time. So, I thought I could upgrade to Marshmallow and downgrade later, but the update said that I could not go back to an older version. Reading some experiences about people that tried to go from Lollipop back to Kitkat and bricked their phones, I have some questions:
If I upgrade to Marshmallow and therefore, the bootloader, will I be unable to flash the stock Lollipop ROM?
If I receive and install an OTA update while running the downgraded Lollipop, will my phone get bricked?
I will try to capture the update's download link. Will I be able to flash it using the stock recovery and go to Marshmallow without any kind of trouble?
I have these questions mainly because I don't want to unlock the bootloader because of the warranty, nor brick my phone.
Fabian TFMI said:
I received the Marshmallow OTA on my phone today, and searching about it made me concerned about some things, in special Bluetooth and battery life; the first because I use Bluetooth to connect to my stereo, the latter because this phone can get over 12 hours of Screen-on Time. So, I thought I could upgrade to Marshmallow and downgrade later, but the update said that I could not go back to an older version. Reading some experiences about people that tried to go from Lollipop back to Kitkat and bricked their phones, I have some questions:
If I upgrade to Marshmallow and therefore, the bootloader, will I be unable to flash the stock Lollipop ROM?
If I receive and install an OTA update while running the downgraded Lollipop, will my phone get bricked?
I will try to capture the update's download link. Will I be able to flash it using the stock recovery and go to Marshmallow without any kind of trouble?
I have these questions mainly because I don't want to unlock the bootloader because of the warranty, nor brick my phone.
Click to expand...
Click to collapse
I don't think downgrading is really a risk you wanna take. Flashing previous factory images over new firmwares have resulted in bricks in the past due to bootloader and modem not being able to downgrade. However, if you want to take that risk, its on you. I will adivse against this.
I can't definitively answer your questions, but I would like to know how you are getting 12 hours SOT... the best I have ever gotten was 6 hours and that was sitting in my chair on WiFi with near perfect signal using it constantly, a "typical" day is about 4 hours SOT over 16-18 hours of usage.
On another note, the change from Lollipop to Marshmallow did effect battery life, but not significantly and it depends on usage... if you have the screen on a lot it is reduced slightly, at the tradeoff of a "better" display (brighter/crisper) from some kernel changes, if you can meet the criteria for Doze Mode (phone not moving, completely idle) idle battery life is increased significantly. As far as BT goes, I use a Plantronics Voyager Legend headset all the time and I've never had any issues on Lollipop or Marshmallow.
acejavelin said:
I can't definitively answer your questions, but I would like to know how you are getting 12 hours SOT... the best I have ever gotten was 6 hours and that was sitting in my chair on WiFi with near perfect signal using it constantly, a "typical" day is about 4 hours SOT over 16-18 hours of usage.
Click to expand...
Click to collapse
To me, a phone is just a (smaller) web browser, so I have adapted it to my usage. This includes enaling Adaptive Brightness on a dim room to get a lower brightness; disabling every kind of non-essential app, like Google and system apps; disabling cookies and specially Javascript on Chrome. This will usually get me 10 hours or so of Screen-on time.
The one time that I got 12 hours of SOT was due my carrier being unable of solving their own problems leaving me without their signal and unable to roam to their partner carrier. I went to *#*#4636#*#* and disabled the radio and it stopped the battery drain from Android O.S., because it can't seem to stop using the radio to whatever it is doing.
acejavelin said:
On another note, the change from Lollipop to Marshmallow did effect battery life, but not significantly and it depends on usage... if you have the screen on a lot it is reduced slightly, at the tradeoff of a "better" display (brighter/crisper) from some kernel changes, if you can meet the criteria for Doze Mode (phone not moving, completely idle) idle battery life is increased significantly. As far as BT goes, I use a Plantronics Voyager Legend headset all the time and I've never had any issues on Lollipop or Marshmallow.
Click to expand...
Click to collapse
Brighter display is something I would really hate, I already think that the display on Lollipop is too bright, even when set to minimum brightness. Was this changed with the update?
Fabian TFMI said:
To me, a phone is just a (smaller) web browser, so I have adapted it to my usage. This includes enaling Adaptive Brightness on a dim room to get a lower brightness; disabling every kind of non-essential app, like Google and system apps; disabling cookies and specially Javascript on Chrome. This will usually get me 10 hours or so of Screen-on time.
The one time that I got 12 hours of SOT was due my carrier being unable of solving their own problems leaving me without their signal and unable to roam to their partner carrier. I went to *#*#4636#*#* and disabled the radio and it stopped the battery drain from Android O.S., because it can't seem to stop using the radio to whatever it is doing.
Brighter display is something I would really hate, I already think that the display on Lollipop is too bright, even when set to minimum brightness. Was this changed with the update?
Click to expand...
Click to collapse
Yes... Many users on lollipop noted the display was slightly yellowish and fuzzy or slightly blurred at times, Motorola seems to have eliminated this issue with some kernel tweaks and probably a color pallette profile update to increase contrast... Several users have stated the display is improved, especially in bright light conditions, but it all seems at the cost of some battery life.
Sent from my MotoG3 using Tapatalk
Dom3616 said:
Flashing previous factory images over new firmwares have resulted in bricks in the past due to bootloader and modem not being able to downgrade.
Click to expand...
Click to collapse
Modifying update-script and commenting bootloader and modem flash, in order to not update them, is not possibile to update only system (patching files) and boot partition (overwriting them) to have MM having the possibility of downgrade to LP providing nandroid backups of system and boot through fastboot flash?
Osid said:
Modifying update-script and commenting bootloader and modem flash, in order to not update them, is not possibile to update only system (patching files) and boot partition (overwriting them) to have MM having the possibility of downgrade to LP providing nandroid backups of system and boot through fastboot flash?
Click to expand...
Click to collapse
You can go back and forth to lollipop from Marshmallow as long as you don't downgrade the bootloader. Modem is not a problem. You can downgrade it.
I personally downgraded to lollipop yesterday using fastboot. And the only thing I didn't downgrade is the bootloader. Today I received the MM ota again and installed it. So far, zero issue.
My phone got bricked after trying to downgrade from MM to LP
Yousvel said:
You can go back and forth to lollipop from Marshmallow as long as you don't downgrade the bootloader. Modem is not a problem. You can downgrade it.
I personally downgraded to lollipop yesterday using fastboot. And the only thing I didn't downgrade is the bootloader. Today I received the MM ota again and installed it. So far, zero issue.
Click to expand...
Click to collapse
Hello, yesterday I was trying to downgrade from MM to LP using Fastboot and by mystake I flashed "fastboot flash partition gpt.bin" and it failed, the others commands failed as well, after that I was unable to turn on my device, it only let me access to Bootloader Mode and also shows the battery charging, cannot access to recovery, and it shows black screen when I try to turn it on.
My phone is completely stock, It has neve been rooted, stock recovery. Its a Moto G XT1540.
Is there a way to bring my phone back to life? What can I do?
JulesSDK said:
Hello, yesterday I was trying to downgrade from MM to LP using Fastboot and by mystake I flashed "fastboot flash partition gpt.bin" and it failed, the others commands failed as well, after that I was unable to turn on my device, it only let me access to Bootloader Mode and also shows the battery charging, cannot access to recovery, and it shows black screen when I try to turn it on.
My phone is completely stock, It has neve been rooted, stock recovery. Its a Moto G XT1540.
Is there a way to bring my phone back to life? What can I do?
Click to expand...
Click to collapse
While in bootloader mode, reboot to factory mode, then reboot again to bootloader mode, flash stock lollipop again without flashing partition and bootloader. You should be good.
Yousvel said:
While in bootloader mode, reboot to factory mode, then reboot again to bootloader mode, flash stock lollipop again without flashing partition and bootloader. You should be good.
Click to expand...
Click to collapse
When I try to reboot to factory mode the screen gets freezed, so, it does not let me to flash stock lollipop, it fails.
JulesSDK said:
When I try to reboot to factory mode the screen gets freezed, so, it does not let me to flash stock lollipop, it fails.
Click to expand...
Click to collapse
Press and hold power button and volume down at the same time for 10 seconds and the phone should boot to bootloader. Then flash lollipop without flashing partition and bootloader. You will be good! I had the same problem with you and that's how I solved it.
Yousvel said:
Press and hold power button and volume down at the same time for 10 seconds and the phone should boot to bootloader. Then flash lollipop without flashing partition and bootloader. You will be good! I had the same problem with you and that's how I solved it.
Click to expand...
Click to collapse
I upgraded my phone to marshmallow, that's the version installed on the phone. I didn't root it nor unlocked the bootloader, and therefore I don't have a custom recovery. The phone does boot bootloader, and when I try to flash stock lollipop without flashing partition and bootloader, like you said, it only lets me flash logo and recovery, but 'boot' and 'system' fails.
These are the errors:
C:\Users\Casa\Desktop\Nueva carpeta (3)>fastboot flash boot boot.img
target reported max download size of 268435456 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.520s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.058s
C:\Users\Casa\Desktop\Nueva carpeta (3)>fastboot flash system system.img_sparsechunk.0
target reported max download size of 268435456 bytes
sending 'system' (262141 KB)...
OKAY [ 8.226s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.682s
Yousvel said:
You can go back and forth to lollipop from Marshmallow as long as you don't downgrade the bootloader. Modem is not a problem. You can downgrade it.
I personally downgraded to lollipop yesterday using fastboot. And the only thing I didn't downgrade is the bootloader. Today I received the MM ota again and installed it. So far, zero issue.
Click to expand...
Click to collapse
Is there any way to know how did you downgrade? A mini tuto for people without extensive knowledge on flashing?
The process would be unlock bootloader, then reboot in recovery, do a factory reset, return to bootloader and flash? Which commands should be included/avoided from typical flashing?
Thank you in advance! I'm suffering reboots and other problems with Marshmallow...
JulesSDK said:
I upgraded my phone to marshmallow, that's the version installed on the phone. I didn't root it nor unlocked the bootloader, and therefore I don't have a custom recovery. The phone does boot bootloader, and when I try to flash stock lollipop without flashing partition and bootloader, like you said, it only lets me flash logo and recovery, but 'boot' and 'system' fails.
These are the errors:
C:\Users\Casa\Desktop\Nueva carpeta (3)>fastboot flash boot boot.img
target reported max download size of 268435456 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.520s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.058s
C:\Users\Casa\Desktop\Nueva carpeta (3)>fastboot flash system system.img_sparsechunk.0
target reported max download size of 268435456 bytes
sending 'system' (262141 KB)...
OKAY [ 8.226s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.682s
Click to expand...
Click to collapse
You cannot downgrade with the bootloader locked, it must be unlocked.
FWIW... Pre-flash validation error is bad especially if any other part actually took, most people who get stuck at this point with a locked bootloader, and no way to unlock it (meaning you didn't previously turn on OEM Unlocking in developer options), have no recourse but to send their device into Motorola for repair/replacement. Note that it will return factory fresh with current software release (Marshmallow) installed. Motorola does not officially support downgrading of the system.
Fabian TFMI said:
I received the Marshmallow OTA on my phone today, and searching about it made me concerned about some things, in special Bluetooth and battery life; the first because I use Bluetooth to connect to my stereo, the latter because this phone can get over 12 hours of Screen-on Time. So, I thought I could upgrade to Marshmallow and downgrade later, but the update said that I could not go back to an older version. Reading some experiences about people that tried to go from Lollipop back to Kitkat and bricked their phones, I have some questions:
If I upgrade to Marshmallow and therefore, the bootloader, will I be unable to flash the stock Lollipop ROM?
If I receive and install an OTA update while running the downgraded Lollipop, will my phone get bricked?
I will try to capture the update's download link. Will I be able to flash it using the stock recovery and go to Marshmallow without any kind of trouble?
I have these questions mainly because I don't want to unlock the bootloader because of the warranty, nor brick my phone.
Click to expand...
Click to collapse
Let me tell you one thing if you have upgraded yr Moto G 2015 to MM and for some reason you wanted to revert back to Lollipop 5.1.1 you can do that... But remember you need to flash stock ROM with unlocked bootloader..
The time when you upgraded yr Moto G 2015 to MM the bootloader gets upgraded and bootloader downgrade can result in hard brick.
So when you flash stock Lollipop 5.1.1 stock ROM skip flashing gpt.bin and bootloader.img files and flash the rest files and you will be in Lollipop with the better battery life.
---------- Post added at 08:30 AM ---------- Previous post was at 08:26 AM ----------
JulesSDK said:
I upgraded my phone to marshmallow, that's the version installed on the phone. I didn't root it nor unlocked the bootloader, and therefore I don't have a custom recovery. The phone does boot bootloader, and when I try to flash stock lollipop without flashing partition and bootloader, like you said, it only lets me flash logo and recovery, but 'boot' and 'system' fails.
These are the errors:
C:\Users\Casa\Desktop\Nueva carpeta (3)>fastboot flash boot boot.img
target reported max download size of 268435456 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.520s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.058s
C:\Users\Casa\Desktop\Nueva carpeta (3)>fastboot flash system system.img_sparsechunk.0
target reported max download size of 268435456 bytes
sending 'system' (262141 KB)...
OKAY [ 8.226s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.682s
Click to expand...
Click to collapse
Yr procedure is correct but the problem that is not allowing you to flash the system files is bcoz you haven't unlocked the bootloader of yr phone..
Unlock yr phone's bootloader and flash again... Sure it will flash all files...
Already did these steps xD
Yousvel said:
While in bootloader mode, reboot to factory mode, then reboot again to bootloader mode, flash stock lollipop again without flashing partition and bootloader. You should be good.
Click to expand...
Click to collapse
XT 1550 moto g3 2 GB version
Rooted , bootloader unlocked
How can I upgrade to marshmallow
Wayne_Bruce said:
XT 1550 moto g3 2 GB version
Rooted , bootloader unlocked
How can I upgrade to marshmallow
Click to expand...
Click to collapse
Follow this guide here: http://forum.xda-developers.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750
Related
Hi all,
Looking for some insight here. I have a second-hand Nexus S GT-I9020A that was replaced because it would no longer boot. I took on the challenge of trying to fix it. Based on the reading I've done so far it may have bad a bad NAND chip, but I'm too stubborn to give up on it just yet. Here are the symptoms:
When booting normally, it hangs on the Google screen with all 4 hardware buttons lit up.
Fastboot works, however I can't flash anything because its bootloader is locked, which brings me to my next point.
When issuing the command fastboot oem unlock, I am prompted with the familiar Yes/no screen but when selecting Yes, nothing seems to happen. I've left it for about 6-7 hours and came back to a message in my PC command window stating "Status read Failed (too many links)".
I can get into the stock recovery but that's really of no help at all. I can wipe cache partition without an issue but get an error when trying to wipe data/factory reset.
I've attempted the One-Click UnBrick software which I read somewhere is compatible with the Nexus S. It did recognize the phone, send a command, and give a success message. The phone rebooted but nothing changed.
So, this leaves me with nothing left to try but to post here. It seems that since I cannot even unlock the bootloader that my hands are tied. Are there any other tools that I should be aware of that can diagnose bad NAND flash? I don't want to toss the phone until I know I've tried everything I can to troubleshoot.
Any help is greatly appreciated. I tried to give as much detail about the problem as I could but if I left out any important info let me know.
Thanks!
Same issue
stevz34 said:
Hi all,
Looking for some insight here. I have a second-hand Nexus S GT-I9020A that was replaced because it would no longer boot. I took on the challenge of trying to fix it. Based on the reading I've done so far it may have bad a bad NAND chip, but I'm too stubborn to give up on it just yet. Here are the symptoms:
When booting normally, it hangs on the Google screen with all 4 hardware buttons lit up.
Fastboot works, however I can't flash anything because its bootloader is locked, which brings me to my next point.
When issuing the command fastboot oem unlock, I am prompted with the familiar Yes/no screen but when selecting Yes, nothing seems to happen. I've left it for about 6-7 hours and came back to a message in my PC command window stating "Status read Failed (too many links)".
I can get into the stock recovery but that's really of no help at all. I can wipe cache partition without an issue but get an error when trying to wipe data/factory reset.
I've attempted the One-Click UnBrick software which I read somewhere is compatible with the Nexus S. It did recognize the phone, send a command, and give a success message. The phone rebooted but nothing changed.
So, this leaves me with nothing left to try but to post here. It seems that since I cannot even unlock the bootloader that my hands are tied. Are there any other tools that I should be aware of that can diagnose bad NAND flash? I don't want to toss the phone until I know I've tried everything I can to troubleshoot.
Any help is greatly appreciated. I tried to give as much detail about the problem as I could but if I left out any important info let me know.
Thanks!
Click to expand...
Click to collapse
I have the same problem wit an I9020T for australia and would appreciate any advice available as well.
Send to samsung service
stevz34 said:
Hi all,
Looking for some insight here. I have a second-hand Nexus S GT-I9020A that was replaced because it would no longer boot. I took on the challenge of trying to fix it. Based on the reading I've done so far it may have bad a bad NAND chip, but I'm too stubborn to give up on it just yet. Here are the symptoms:
When booting normally, it hangs on the Google screen with all 4 hardware buttons lit up.
Fastboot works, however I can't flash anything because its bootloader is locked, which brings me to my next point.
When issuing the command fastboot oem unlock, I am prompted with the familiar Yes/no screen but when selecting Yes, nothing seems to happen. I've left it for about 6-7 hours and came back to a message in my PC command window stating "Status read Failed (too many links)".
I can get into the stock recovery but that's really of no help at all. I can wipe cache partition without an issue but get an error when trying to wipe data/factory reset.
I've attempted the One-Click UnBrick software which I read somewhere is compatible with the Nexus S. It did recognize the phone, send a command, and give a success message. The phone rebooted but nothing changed.
So, this leaves me with nothing left to try but to post here. It seems that since I cannot even unlock the bootloader that my hands are tied. Are there any other tools that I should be aware of that can diagnose bad NAND flash? I don't want to toss the phone until I know I've tried everything I can to troubleshoot.
Any help is greatly appreciated. I tried to give as much detail about the problem as I could but if I left out any important info let me know.
Thanks!
Click to expand...
Click to collapse
Try flashing the official Android 4.1.2 image from Google in fastboot. See if it boots... Then maybe you will have more luck unlocking it! I would also try to wipe as many thing as possible before doing it. Try system, data, boot, cache, dalvik... Even sdcard might help...
Dark_Eyes_ said:
Try flashing the official Android 4.1.2 image from Google in fastboot. See if it boots... Then maybe you will have more luck unlocking it! I would also try to wipe as many thing as possible before doing it. Try system, data, boot, cache, dalvik... Even sdcard might help...
Click to expand...
Click to collapse
Tried this but as said fastboot is not recognised by my pc. Have installed almost all the drivers I can find to no avail. Must be something else to try.
Spanner127 said:
Tried this but as said fastboot is not recognised by my pc. Have installed almost all the drivers I can find to no avail. Must be something else to try.
Click to expand...
Click to collapse
Well, you should be able to flash official Google images in stock recovery too... Have you tried that?
Dark_Eyes_ said:
Well, you should be able to flash official Google images in stock recovery too... Have you tried that?
Click to expand...
Click to collapse
mY COMPUTER ONLY RECOGNISES abd IN SIDELOAD MODE. tHE FASTBOOT ANYTHING IS NOT RECOGNISED SO i CANNOT UPDATE OR FIX anything. Thanks for trying.
Can you try doing all the stuff you did in some another PC.
Worth a try.
Dark_Eyes_ said:
Try flashing the official Android 4.1.2 image from Google in fastboot. See if it boots... Then maybe you will have more luck unlocking it! I would also try to wipe as many thing as possible before doing it. Try system, data, boot, cache, dalvik... Even sdcard might help...
Click to expand...
Click to collapse
Tried as suggested, received the following output:
C:\Users\Steven\Downloads\sojua-jzo54k>flash-all
sending 'bootloader' (1536 KB)...
OKAY [ 0.187s]
writing 'bootloader'...
FAILED (remote: Bootloader Locked - Use "fastboot oem unlock" to Unlock)
finished. total time: 0.203s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
< waiting for device >
sending 'radio' (12288 KB)...
OKAY [ 1.543s]
writing 'radio'...
FAILED (remote: Bootloader Locked - Use "fastboot oem unlock" to Unlock)
finished. total time: 1.543s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
< waiting for device >
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: I9020XXKA3
Baseband Version.....: I9020UCKF1
Serial Number........: 33311A4C1F8500EC
--------------------------------------------
checking product...
OKAY [ 0.016s]
checking version-bootloader...
FAILED
Device version-bootloader is 'I9020XXKA3'.
Update requires 'I9020XXLC2'.
finished. total time: 0.016s
Press any key to exit...
It would seem that I can't flash anything, including official firmware, if the bootloader is locked?
On the plus side, the phone responds fine to the fastboot commands and seems to transfer the images to it just fine, just still no luck getting the darn bootloader unlocked
stevz34 said:
Tried as suggested, received the following output:
C:\Users\Steven\Downloads\sojua-jzo54k>flash-all
sending 'bootloader' (1536 KB)...
OKAY [ 0.187s]
writing 'bootloader'...
FAILED (remote: Bootloader Locked - Use "fastboot oem unlock" to Unlock)
finished. total time: 0.203s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
< waiting for device >
sending 'radio' (12288 KB)...
OKAY [ 1.543s]
writing 'radio'...
FAILED (remote: Bootloader Locked - Use "fastboot oem unlock" to Unlock)
finished. total time: 1.543s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
< waiting for device >
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: I9020XXKA3
Baseband Version.....: I9020UCKF1
Serial Number........: 33311A4C1F8500EC
--------------------------------------------
checking product...
OKAY [ 0.016s]
checking version-bootloader...
FAILED
Device version-bootloader is 'I9020XXKA3'.
Update requires 'I9020XXLC2'.
finished. total time: 0.016s
Press any key to exit...
It would seem that I can't flash anything, including official firmware, if the bootloader is locked?
On the plus side, the phone responds fine to the fastboot commands and seems to transfer the images to it just fine, just still no luck getting the darn bootloader unlocked
Click to expand...
Click to collapse
Normally it is possible to flash official ota from Google even if the bootloader is locked. What version did you have prior to your problems? Try flashing the ota package that came just after your version as it seems that the package your are trying with cannot be flashed over the version that you have right now!
Dark_Eyes_ said:
Normally it is possible to flash official ota from Google even if the bootloader is locked. What version did you have prior to your problems? Try flashing the ota package that came just after your version as it seems that the package your are trying with cannot be flashed over the version that you have right now!
Click to expand...
Click to collapse
Currently the phone has 2.3.6. I tried flashing 4.0.4, which was the next one, and it failed with the same error, indicating I need to unlock my bootloader. Also tried flashing the 2.3.6 firmware, received the same error. I'm starting to think I should probably give up on this phone.
Any more suggestions?
stevz34 said:
Currently the phone has 2.3.6. I tried flashing 4.0.4, which was the next one, and it failed with the same error, indicating I need to unlock my bootloader. Also tried flashing the 2.3.6 firmware, received the same error. I'm starting to think I should probably give up on this phone.
Any more suggestions?
Click to expand...
Click to collapse
Did you try the OTA update from Google? That's weird cause I flashed it back then and I was on stock 2.3.6 with locked bootloader and stock recovery and it worked. Have you don't anything particular with your phone or is it pure stock 2.3.6? Start there
http://forum.xda-developers.com/showthread.php?t=1063664
Dark_Eyes_ said:
Did you try the OTA update from Google? That's weird cause I flashed it back then and I was on stock 2.3.6 with locked bootloader and stock recovery and it worked. Have you don't anything particular with your phone or is it pure stock 2.3.6? Start there
http://forum.xda-developers.com/showthread.php?t=1063664
Click to expand...
Click to collapse
Thanks for posting that link. Still no luck though. I tried the 2.3.6 (GRK39C) -> 2.3.6 (GRK39F) OTA file and the 2.3.6 (GRK39F) -> 4.0.4 one as I am not sure which version of 2.3.6 that I have. Basically I am trying to use fastboot to apply the OTA update using fastboot -w update filename.zip however it is failing with the following message:
C:\Users\Steven\Downloads>fastboot -w update d1be8195481a.signed-sojua-GRK39F-fr
om-GRK39C.d1be8195.zip
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
C:\Users\Steven\Downloads>
The OTA updates indicate they can be flashed using stock recovery. However when I enter the recovery on the phone and select update from sdcard, I get the message indicating that it cannot mount /sdcard. Is there another way I should be doing this?
stevz34 said:
Thanks for posting that link. Still no luck though. I tried the 2.3.6 (GRK39C) -> 2.3.6 (GRK39F) OTA file and the 2.3.6 (GRK39F) -> 4.0.4 one as I am not sure which version of 2.3.6 that I have. Basically I am trying to use fastboot to apply the OTA update using fastboot -w update filename.zip however it is failing with the following message:
C:\Users\Steven\Downloads>fastboot -w update d1be8195481a.signed-sojua-GRK39F-fr
om-GRK39C.d1be8195.zip
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
C:\Users\Steven\Downloads>
The OTA updates indicate they can be flashed using stock recovery. However when I enter the recovery on the phone and select update from sdcard, I get the message indicating that it cannot mount /sdcard. Is there another way I should be doing this?
Click to expand...
Click to collapse
You have to rename the file to update.zip and place it on /sdcard. It will install it automatically. Stock recovery won't install custom zip file so that's why you need to do that. Let me know if it works...
So my friend gave me her old first gen Moto G (XT1032 from Telus in Canada) because it stopped working for her. She told me nothing special happened before and she did not try to do an update. I have no way to know what version of Android the device was running before it bricked. I am familiar with Android devices but mostly Nexus phones so I thought I could try to fix it myself. So right now, here is what it does :
- If I try to turn it on, it stays stuck on the Motorola logo
- If I try to go in the bootloader, I can see it and it says the version number is 41.18 (also the device is locked and was never rooted or anything)
- When in the bootloader, if I try to Normal startup it reboots and stays stuck on the Motorola logo
- If I try to go to recovery or factory reset, the phone just shuts down and nothing happens
I have seen other posts on XDA which seem to relate to the same problem but none of them could fix the one I have. Any help would be much appreciated.
Thanks
Unstable hardware. It happened to me too after throwing on the floor for the 1000th time. The screen is still 100% healthy LoL.
Try returning it if it's still in warranty. If not, try unlocking the bootloader and flashing the latest GPE
Sent from my XT1562 using Tapatalk
Hi,
Seems like firmware goes away... **** happens, even without "throwing" it on the floor a thousand times Unlock it, install a custom recovery (latest Twrp is 2.8.7.0) and flash firmware you want...
If you get an error when flashing, maybe due to your bootloader version... Latest roms require latest bootloader (41.1A). There is a bootloader upgrader tool available in the general section of Moto G forum.
Sorry if I don't give you direct links but I'm on my phone Don't worry, you'll find easily...
Let us know evolution
Can't flash recovery
satanas17 said:
Hi,
Seems like firmware goes away... **** happens, even without "throwing" it on the floor a thousand times Unlock it, install a custom recovery (latest Twrp is 2.8.7.0) and flash firmware you want...
If you get an error when flashing, maybe due to your bootloader version... Latest roms require latest bootloader (41.1A). There is a bootloader upgrader tool available in the general section of Moto G forum.
Sorry if I don't give you direct links but I'm on my phone Don't worry, you'll find easily...
Let us know evolution
Click to expand...
Click to collapse
OK So Im trying to flash TWRP (2.8.6.0) with fastboot but when I do I get 2 errors :
target max-sparse-size: 256MB
sending 'recovery' (8480 KB)...
OKAY [ 10.195s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 15.208s
It seems my recovery partition is not formatted or something. What should I do now ? Also Im on a MAC so I think there is now way for me to update the bootloader which is not at 41.18
I also tried to boot the recovery (both stock and twrp 2.8.6.0 and 2.8.7.0) instead of flashing it by doing this :
fastboot boot recovery.img
I get this :
downloading 'boot.img'...
OKAY [ 5.330s]
booting...
FAILED (remote failure)
finished. total time: 15.383s
Im not sure where the boot.img is supposed to come from. Am I doing something wrong?
Thanks!
Hello!
I tried to make a downgrade of my XT1039 from Lolipop to Kit Kat.
My XT1039 bootloader is unlock (I have status3 in the fastboot menu) but when I try to flash the kit kat stock rom I see this:
writing 'partition' ...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.352s
I am not an expert but I think that from this point the rest of commands are not applied. After finishing the flash I reboot the device and it get's stuck in the bootanimation.
I don't know what to do. I red that is not possible to recover if the device was already updated to Lolipop but I am not sure. Should I try a Cyanogen firmware?
Any advice please?
Thanks you so much
This is a dangerous way to downgrade to KitKat. People have dead phones by flashing an older Bootloader.
You can safely flash one of these Stock KitKat ROMs: http://forum.xda-developers.com/moto-g/4g-development/rom-stock-motorola-4g-kitkat-rom-t3160127
If you choose an Untouched ROM - Do not accept OTA Updates. Such updates are disabled in the Optimized ROMs.
OK, thak you very much.
Stock, unrooted xt1540. Got the update notification this morning, so excited. After updating, it's boot looping and the M logo is the furthest it can go.
Tried to fastboot flash back to old 5.1.1 factory image, "image validation failed". Maybe because boot loader got updated and won't roll back?
All I can think of now is to wait for the 6.0 factory image and try that again, but I may end up waiting for it too long.
Any suggestions? Thanks!
What about the images at http://forum.xda-developers.com/2015-moto-g/general/ota-moto-g3-marshmallow-ota-links-t3284308
Try in fastboot clear the cache and data ...
have you tried using twrp to just install a cm rom or something similar?
worst case scenario you can use twrp to force the soak test images onto their respective partitions. if your bootloader was updated the soak test will run...even if it bootloops for any reason, then at least you've taken one step forward again.
MrTooPhone said:
What about the images at http://forum.xda-developers.com/2015-moto-g/general/ota-moto-g3-marshmallow-ota-links-t3284308
Click to expand...
Click to collapse
I wish I could resume the OTA, even manually, but right now I can only go to bootloader, not even the stock recovery....Thanks for the idea, though! Really appreciate it.
hp420 said:
have you tried using twrp to just install a cm rom or something similar?
worst case scenario you can use twrp to force the soak test images onto their respective partitions. if your bootloader was updated the soak test will run...even if it bootloops for any reason, then at least you've taken one step forward again.
Click to expand...
Click to collapse
I just tried flash in the twrp.img, got declined by bootloader again...
Now is there factory images for the soak test? Thanks!!
lexer98 said:
Try in fastboot clear the cache and data ...
Click to expand...
Click to collapse
clearing cache went through, but clearing data failed. Rebooting to bootloader mode and try returning to stock again, still no go...
In fastboot mode, I can flast logo, fsg, NON-HLOS, bootloader, recovery -- all from 5.1.1 factory image, but when I tried to flash boot or system chunks, it says:
D:\Desktop\g\Mfastboot>fastboot flash system system.img_sparsechunk.0
target reported max download size of 268435456 bytes
sending 'system' (262141 KB)...
OKAY [ 10.573s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 11.042s
Is my only option to wait for the MM factory image....
alvin612 said:
I just tried flash in the twrp.img, got declined by bootloader again...
Now is there factory images for the soak test? Thanks!!
Click to expand...
Click to collapse
Well....yes and no.
http://forum.xda-developers.com/201...-devs-moto-g3-xt1540-soak-test-files-t3255643
The images all flash in fastboot except the system one, which requires using adb shell while booted to twrp. You have to use a dd command to force the system.img into the correct partition.
Earlier today I had to give up on this osprey because of limited bandwith for fix.
Thanks again for everyone's help!!
My phone got bricked after trying to downgrade from MM to LP
Hello, yesterday I was trying to downgrade from MM to LP using Fastboot and by mystake I flashed "fastboot flash partition gpt.bin" and it failed, the others commands failed as well, after that I was unable to turn on my device, it only let me access to Bootloader Mode and also shows the battery charging, cannot access to recovery, and it shows black screen when I try to turn it on.
My phone is completely stock, It has neve been rooted, stock recovery. Its a Moto G XT1540. the Bootloader is locked.
Is there a way to bring my phone back to life? What can I do?
JulesSDK said:
Hello, yesterday I was trying to downgrade from MM to LP using Fastboot and by mystake I flashed "fastboot flash partition gpt.bin" and it failed, the others commands failed as well, after that I was unable to turn on my device, it only let me access to Bootloader Mode and also shows the battery charging, cannot access to recovery, and it shows black screen when I try to turn it on.
My phone is completely stock, It has neve been rooted, stock recovery. Its a Moto G XT1540. the Bootloader is locked.
Is there a way to bring my phone back to life? What can I do?
Click to expand...
Click to collapse
I contacted Motorola. Warranty covers my situation. Going to ask for a replacement.
JulesSDK said:
Hello, yesterday I was trying to downgrade from MM to LP using Fastboot and by mystake I flashed "fastboot flash partition gpt.bin" and it failed, the others commands failed as well, after that I was unable to turn on my device, it only let me access to Bootloader Mode and also shows the battery charging, cannot access to recovery, and it shows black screen when I try to turn it on.
My phone is completely stock, It has neve been rooted, stock recovery. Its a Moto G XT1540. the Bootloader is locked.
Is there a way to bring my phone back to life? What can I do?
Click to expand...
Click to collapse
Unlock the bootloader and then try flashing. I was in a similar situation once, was getting failed messages when trying to flash official signed factory images. Unlocked the bootloader and then tried to flash and voila, everything flashed smoothly. No harm in trying unless you are worried about warranty.
Hi. I got a Moto Maxx with Android Marshmallow (Telcel carrier).
After trying several roms, I decided to go back to stock, since I couldn't find a Marshmallow rom, I decided to update from 4.4. I installed "Mexico Retail Stock Kitkat /// RETLA_XT1225_4.4.4_KXG21.50-9_cid12_subsidy-DEFAULT_CFC.xml.zip" from this thread. Everything went fine, although I lost the custom recovery during the process.
Then, from the software updater option on the phone, I updated to Lollipop. Unfortunately, it didn't updated. Instead, I got a bricked phone. It didn't turned on.
In order to recover it. I followed this guide. The phone turned on again, and now I am stuck on an "empty" bootloader. The upper half of the screen only shows "Start", similar to the picture from the guide.
But I can't flash any stock rom. It seems by doing the steps of that guide, I re-locked my phone. I can't unlock it because, while I know my unlock bootloader code, mfastboot tells me I must enable "Enable OEM Unlock" in the developer settings (which I can't reach).
Trying to flash any stock rom gives me the following errors:
Code:
[B]>mfastboot flash partition gpt.bin[/B]
[I]target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.020s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.104s[/I]
>[B]mfastboot flash bootloader bootloader.img[/B]
[I]target max-sparse-size: 256MB
sending 'bootloader' (2159 KB)...
OKAY [ 0.112s]
writing 'bootloader'...
[B](bootloader) Motoboot: Unknown partition name[/B]
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.202s[/I]
>[B]mfastboot flash radio radio.img[/B]
[I]target max-sparse-size: 256MB
sending 'radio' (85457 KB)...
OKAY [ 2.753s]
writing 'radio'...
[B](bootloader) Motoboot: Unknown partition name[/B]
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 2.802s[/I]
>[B]mfastboot.exe flash system system.img_sparsechunk.0[/B]
[I]target max-sparse-size: 256MB
sending 'system' (253363 KB)...
OKAY [ 8.205s]
writing 'system'...
[B](bootloader) Permission denied[/B]
FAILED (remote failure)
finished. total time: 8.226s[/I]
I can't access to recovery. Please, help me :crying::crying::crying:
Why do people relock their bootloader?
With an unlocked bootloader you can flash other region images, if necessary, like Brazil. With locked bootloader your need Mexico. Your may even need your carrier firmware.
ChazzMatt said:
Why do people relock their bootloader?
Click to expand...
Click to collapse
It wasn't my intention. The phone bricked, and in order to return to bootloader I followed that guide. It worked but it seems that during the process it locked the phone.
But you went from Marshmallow 6.0.1 back to Lollipop 5.0.2. You can't do that unless you omit gpt.bin in your flash commands. Otherwise you will get bootloop or brick your phone.
I assume at one time you had stock Marshmallow on the phone before trying custom ROMs? Or at the least, probably had flashed Marshmallow radio and bootloader?
With unlocked bootloader you can downgrade back to Lollipop or Kitkat, but you need to omit gpt.bin.
I would also omit recovery.img, to keep TWRP.
---------- Post added at 03:23 PM ---------- Previous post was at 03:14 PM ----------
See this thread, but you'll need your region firmware.
https://forum.xda-developers.com/showthread.php?t=3662683
ChazzMatt said:
But you went from Marshmallow 6.0.1 back to Lollipop 5.0.2. You can't do that unless you omit gpt.bin in your flash commands. Otherwise you will get bootloop or brick your phone.
I assume at one time you had stock Marshmallow on the phone before trying custom ROMs? Or at the least, probably had flashed Marshmallow radio and bootloader?
With unlocked bootloader you can downgrade back to Lollipop or Kitkat, but you need to omit gpt.bin.
I would also omit recovery.img, to keep TWRP.
Click to expand...
Click to collapse
Yes, as I said. The phone had Stock Marshmallow. I unlocked my bootloader, I tried custom roms, tried TWRP, I even could go back to stock KitKat (by omitting gpt.bin)
The problem came when I accepted to update to OTA Lollipop. The phone bricked; the screen didn't turned on. And while I found a guide that could unbrick the phone, I ended without recovery and with a relocked phone.
jairjy said:
Yes, as I said. The phone had Stock Marshmallow. I unlocked my bootloader, I tried custom roms, tried TWRP, I even could go back to stock KitKat (by omitting gpt.bin)
The problem came when I accepted to update to OTA Lollipop. The phone bricked; the screen didn't turned on. And while I found a guide that could unbrick the phone, I ended without recovery and with a relocked phone.
Click to expand...
Click to collapse
Because while you had downgraded to Kitkat, but you still had Marshmallow bootloader. You can't take OTA, because it will install bootloader and you cannot downgrade bootloader.
Have we discussed this before, because someone else did EXACTLY the same thing. Downgraded to Kitkat, then tried to take Lollipop OTA --which tries to install Lollipop bootloader!