Related
RSD completes but I still have CM10 no matter what I do.
I am having problems with my phone so I was gonna go back to stock but I realized RSD completes but the phone still boots into CM10 and factory reset/wipe does nothing in recovery.
What can I try?
Flash another rom?
sent from my thumbs
Firstly there is a dedicated CM10 Q&A thread so you could have avoided a new thread & be getting more responses. Now you can post in there with more details of your phone original stock firmware to the steps you worked up to CM10 & finally what fxz are you flashing to go back to stock so that some one may be able to help you.
sounreal said:
RSD completes but I still have CM10 no matter what I do.
I am having problems with my phone so I was gonna go back to stock but I realized RSD completes but the phone still boots into CM10 and factory reset/wipe does nothing in recovery.
What can I try?
Click to expand...
Click to collapse
Open the XML file using a text editor and check if there is a line containing system.
As a solution, you may open a command prompt in that folder using shift+right click. Put your phone in fastboot mode. Type and hit enter.
Code:
fastboot flash system system.img
Sent from my ME865 using Tapatalk 2
RAD7 said:
Firstly there is a dedicated CM10 Q&A thread so you could have avoided a new thread & be getting more responses.
Click to expand...
Click to collapse
Excuse you but I know you are pretty helpful around here I'm removing cm 10 and going back to stock. I know what I'm doing yet its not working something is physically wrong with the phone I guess. Cm10 worked perfectly fine for about 6 months on the phone. im using whatever att fxz ICS file that is posted. At one point in time I had 3 atrix 2s all on cm10 and I removed them all by rsd to ICS. I have tried every version I could fine of rsd and att fxz file.
Ravikirancg said:
Open the XML file using a text editor and check if there is a line containing system.
As a solution, you may open a command prompt in that folder using shift+right click. Put your phone in fastboot mode. Type and hit enter.
Code:
fastboot flash system system.img
Sent from my ME865 using Tapatalk 2
Click to expand...
Click to collapse
I'm super late... but I flashed everything. Including boot.img preinstall.img radio.img recovery.img fromInlineFlashing_Edison_67.21.125_CFC_P3_APBP and they all say something like
C:\Users\TheOwner\Downloads\InlineFlashing_Edison_67.21.125_CFC_P3_APBP.xml>fast
boot flash system system.img
target reported max download size of 1056964608 bytes
sending 'system' (491264 KB)...
OKAY [ 23.743s]
writing 'system'...
OKAY [ 14.976s]
finished. total time: 38.719s
I never get a error message. I reboot and CM10 is still on the phone. I how I delete the partitions and then reformat them?
C:\Users\TheOwner\Downloads\InlineFlashing_Edison_67.21.125_CFC_P3_APBP.xml>fast
boot format system
formatting 'system' partition...
FAILED (remote: protocol error)
FAILED (remote: protocol error)
finished. total time: -0.000s
C:\Users\TheOwner\Downloads\InlineFlashing_Edison_67.21.125_CFC_P3_APBP.xml>fast
boot erase system
erasing 'system'...
(bootloader) Command restricted
FAILED (remote: )
finished. total time: 0.016s
sounreal said:
I'm super late... but I flashed everything. Including boot.img preinstall.img radio.img recovery.img fromInlineFlashing_Edison_67.21.125_CFC_P3_APBP and they all say something like
C:\Users\TheOwner\Downloads\InlineFlashing_Edison_67.21.125_CFC_P3_APBP.xml>fast
boot flash system system.img
target reported max download size of 1056964608 bytes
sending 'system' (491264 KB)...
OKAY [ 23.743s]
writing 'system'...
OKAY [ 14.976s]
finished. total time: 38.719s
I never get a error message. I reboot and CM10 is still on the phone. I how I delete the partitions and then reformat them?
C:\Users\TheOwner\Downloads\InlineFlashing_Edison_67.21.125_CFC_P3_APBP.xml>fast
boot format system
formatting 'system' partition...
FAILED (remote: protocol error)
FAILED (remote: protocol error)
finished. total time: -0.000s
C:\Users\TheOwner\Downloads\InlineFlashing_Edison_67.21.125_CFC_P3_APBP.xml>fast
boot erase system
erasing 'system'...
(bootloader) Command restricted
FAILED (remote: )
finished. total time: 0.016s
Click to expand...
Click to collapse
You are like a year late lol
alright,
could you tell me what was your stock version?
and the version name?
and what version of RSD are you using?
Uzayr said:
You are like a year late lol
alright,
could you tell me what was your stock version?
and the version name?
and what version of RSD are you using?
Click to expand...
Click to collapse
4.0.4... I don't remember... A year ago I tried every RSD I could find. After I could not get it to format using fastboot I tried to brick it with RSD using the wrong Asia firmware. They did not do anything.
sounreal said:
4.0.4... I don't remember... A year ago I tried every RSD I could find. After I could not get it to format using fastboot I tried to brick it with RSD using the wrong Asia firmware. They did not do anything.
Click to expand...
Click to collapse
i had similar problems using an older version of rsd/
so i suggest you try RSD Lite 6 and up and see if it works for you.
Alright, could you tell if you A2 is at&t or retail?
i'll try my best to salvage the right fxz for you.
I'm sure I have RSD 6 lite but just so we are on the same page... Can you give me a link to the correct RSD 6 LITE? Oh yeah and its a ATT Atrix 2
sounreal said:
I'm sure I have RSD 6 lite but just so we are on the same page... Can you give me a link to the correct RSD 6 LITE? Oh yeah and its a ATT Atrix 2
Click to expand...
Click to collapse
Link for RSD Lite 6.1.4
http://forum.xda-developers.com/showthread.php?t=2637338
And also for the fxz file..i suggest you try the third link in this page
http://sbf.droid-developers.org/phone.php?device=17
if you were already on 4.0.4 before you flashed cm
I had RSD 6.1.4 installed but I tried 6.1.6 and the same thing happened. Once RSD completed the phone rebooted to the stock android recovery. I Hit the volume keys to bring up the menu and hit reboot... Still have CM 10...
sounreal said:
I had RSD 6.1.4 installed but I tried 6.1.6 and the same thing happened. Once RSD completed the phone rebooted to the stock android recovery. I Hit the volume keys to bring up the menu and hit reboot... Still have CM 10...
Click to expand...
Click to collapse
wait a minute...you don't need to hit the volume keys in recovery.
after fxz the phone should reboot to recovery and complete the other half of the setup.
I read if it and did not touch it once it got to the stock recovery... After about 2 mins it rebooted and I still had CM 10.
Hi, I am fairly new here but I have been around (just leeching, LOL) since my SE X10 Mini.
You could try using RSDLite 5.3.1.
I used it just this morning when I got black screen after flashing things after AOSB.
Just make sure you have the latest Moto Drivers.
Good luck! :good:
Cheers,
Rae
Raeshabu said:
Hi, I am fairly new here but I have been around (just leeching, LOL) since my SE X10 Mini.
You could try using RSDLite 5.3.1.
I used it just this morning when I got black screen after flashing things after AOSB.
Just make sure you have the latest Moto Drivers.
Good luck! :good:
Cheers,
Rae
Click to expand...
Click to collapse
Nope that did not help I still have cm10.
My Xt925 has "Encrytion Unsuccessful" when I boot up. I have tried to flash a recovery img but all I get is this message.
C:\Documents and Settings\Admin\Desktop\Fastbootxt925\Fastboot>fastboot flash re covery twrp-hdrecovery.img
sending 'recovery' (6678 KB)... OKAY [ 0.844s]
writing 'recovery'...
INFOFailed to erase partition INFOFailed to flash partition recovery
FAILED (remote failure) finished. total time: 1.000s
Click to expand...
Click to collapse
Motorola XT925
Android 4.2
AF Fastboot flasmode (s)
10.9B (Sha-5b608bc, 2012-12-20 16:55:20)
eMMC info: size 16gb
Device is unlocked, status code: 3
Its Bricked isn't it?
I have tried getting some help so I hope someone reads this..
"Partition signed?"
is0lde said:
My Xt925 has "Encrytion Unsuccessful" when I boot up. I have tried to flash a recovery img but all I get is this message.
Motorola XT925
Android 4.2
AF Fastboot flasmode (s)
10.9B (Sha-5b608bc, 2012-12-20 16:55:20)
eMMC info: size 16gb
Device is unlocked, status code: 3
Its Bricked isn't it?
I have tried getting some help so I hope someone reads this..
Click to expand...
Click to collapse
I have also tried reflashing rom using RSD Lite, and get a the Following error
Failed flashing process. 2/22 Flash parition "partition signed" -> Phone returned FAIL.
Click to expand...
Click to collapse
is0lde said:
I have also tried reflashing rom using RSD Lite, and get a the Following error
Click to expand...
Click to collapse
Delete the partition signed line from the Xml and try flashing again!!!!
Al the best!!!!
Sent from my C6802 using Tapatalk
Same problem
Hey man, having the same problem, excluded the line (actually many), and it installed 14. Now the reboot is in process and nothing happens.
kumeipark said:
Delete the partition signed line from the Xml and try flashing again!!!!
Al the best!!!!
Sent from my C6802 using Tapatalk
Click to expand...
Click to collapse
mari18cf said:
Hey man, having the same problem, excluded the line (actually many), and it installed 14. Now the reboot is in process and nothing happens.
Click to expand...
Click to collapse
flash the partition file with "Mfastboot", then re-flash the stock file with only the partition, tz, and getvar(you may not have this) removed.
I got an xt1031 on ebay that was flashed to work on Page Plus. I have restored the ROM to falcon_KXB21.14-L1.57.zip but the baseband still says "VZW_CUST" and I get activation stuff when I start it up. How can I get this working like a regular xt1031 again? I am rooted, unlocked and have CWM installed. I also have a regular, working xt1031 if I need anything off of it.
I can't find any information about restoring baseband or anything like that. After flashing the stock ROM I restored the phone.
HardOnChairs said:
I got an xt1031 on ebay that was flashed to work on Page Plus. I have restored the ROM to falcon_KXB21.14-L1.57.zip but the baseband still says "VZW_CUST" and I get activation stuff when I start it up. How can I get this working like a regular xt1031 again? I am rooted, unlocked and have CWM installed. I also have a regular, working xt1031 if I need anything off of it.
I can't find any information about restoring baseband or anything like that. After flashing the stock ROM I restored the phone.
Click to expand...
Click to collapse
Factory Firmware Images are available here: http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Flashing Tutorial: http://forum.xda-developers.com/showthread.php?t=2542219
I would start by only flashing the 'system.img.sparsechunk' files:
mfastboot flash system system.img_sparsechunk1 (CHANGE NAME TO MATCH ACTUAL FILE IN FOLDER)
mfastboot flash system system.img_sparsechunk2 (CHANGE NAME TO MATCH ACTUAL FILE IN FOLDER)
mfastboot flash system system.img_sparsechunk3 (CHANGE NAME TO MATCH ACTUAL FILE IN FOLDER)
mfastboot erase userdata
mfastboot reboot​
lost101 said:
by only flashing
Click to expand...
Click to collapse
Would that be more effective? Because I would be just as happy to flash the entire ROM again and start over if it would work as well.
Edit: nevermind I see what's going on now with the zip
HardOnChairs said:
Would that be more effective? Because I would be just as happy to flash the entire ROM again and start over if it would work as well.
Edit: nevermind I see what's going on now with the zip
Click to expand...
Click to collapse
My recommendation is for your safety. Messing with fastboot has destroyed many phones.
Code:
C:\Users\User\Desktop\New folder>mfastboot devices
'mfastboot' is not recognized as an internal or external command,
operable program or batch file.
C:\Users\User\Desktop\New folder>mfastboot devices
TA96506RJD fastboot
C:\Users\User\Desktop\New folder>mfastboot flash system system.img_sparsechunk1
target max-sparse-size: 256MB
sending 'system' (262084 KB)...
OKAY [ 8.213s]
writing 'system'...
OKAY [ 14.144s]
finished. total time: 22.361s
C:\Users\User\Desktop\New folder>mfastboot flash system system.img_sparsechunk2
target max-sparse-size: 256MB
sending 'system' (256888 KB)...
OKAY [ 8.052s]
writing 'system'...
OKAY [ 12.088s]
finished. total time: 20.142s
C:\Users\User\Desktop\New folder>mfastboot flash system system.img_sparsechunk3
target max-sparse-size: 256MB
sending 'system' (238359 KB)...
OKAY [ 7.485s]
writing 'system'...
OKAY [ 11.907s]
finished. total time: 19.393s
C:\Users\User\Desktop\New folder>mfastboot flash system system.img_sparsechunk4
target max-sparse-size: 256MB
sending 'system' (26644 KB)...
OKAY [ 0.875s]
writing 'system'...
OKAY [ 8.438s]
finished. total time: 9.313s
C:\Users\User\Desktop\New folder>mfastboot erase userdata
erasing 'userdata'...
OKAY [ 0.500s]
finished. total time: 0.500s
C:\Users\User\Desktop\New folder>mfasboot reboot
'mfasboot' is not recognized as an internal or external command,
operable program or batch file.
C:\Users\User\Desktop\New folder>mfastboot reboot
rebooting...
finished. total time: -0.000s
C:\Users\User\Desktop\New folder>
Everything seems to have gone well but I still get the activation screen and the baseband still has VZW_CUST.
Edit: Here are all of the files in the zip for my phone if that helps:
HTML:
boot.img
falcon_boost_user_4.4.4_KXB21.14-L1.57_57_release-keys-cid9.bat
falcon_boost_user_4.4.4_KXB21.14-L1.57_57_release-keys-cid9.xml
fsg.mbn
gpt.bin
logo.bin
mfastboot.exe
motoboot.img
NON-HLOS.bin
recovery.img
system.img_sparsechunk1
system.img_sparsechunk2
system.img_sparsechunk3
system.img_sparsechunk4
Now flash the Radio Firmware only. Use the following fastboot commands:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn​
The baseband says BOOST_CUST now but I am still getting these activation screens that I never get on my other boost phones.
HardOnChairs said:
The baseband says BOOST_CUST now but I am still getting these activation screens that I never get on my other boost phones.
Click to expand...
Click to collapse
From memory, I do recall Verizon software being present in the Boost Firmare Images. But you can delete certain apks to stop those activation screens appearing. If you install TWRP, you can use the file explorer to delete the folders. I will try to get the correct names soon, but you might be able to guess them - they are located in /system/priv-app
The weird this is that it is a boost/sprint app.
com.motorola.android.omadm.sprint.client
Click to expand...
Click to collapse
But I have a bunch of these phones and none of them do this. There are some activation apps, but they are never intrusive like this.
On one hand I'd like to get it to go away any way I can, but I would most prefer all of my devices to be set up the same. Is there anything I can do given that I have an identical model that is set up the right way? I don't know enough about how android partitions work to understand why flashing a stock ROM and resetting it wouldn't make it act exactly the same as my other devices that I have done the same with.
HardOnChairs said:
The weird this is that it is a boost/sprint app.
But I have a bunch of these phones and none of them do this. There are some activation apps, but they are never intrusive like this.
On one hand I'd like to get it to go away any way I can, but I would most prefer all of my devices to be set up the same. Is there anything I can do given that I have an identical model that is set up the right way? I don't know enough about how android partitions work to understand why flashing a stock ROM and resetting it wouldn't make it act exactly the same as my other devices that I have done the same with.
Click to expand...
Click to collapse
Those are the stock activation apps that are needed if you plan to use the phone. Typically, they "go away" or are "unseen" when the device is activated.
Sent from my XT1031
@HardOnChairs - Apologies, I got confused between Verizon and Sprint. There are no Verizon files in the Boost Firmware, only those for Sprint.
The conversion to PagePlus includes flashing the XT1028 Bootloader - so that's still the Bootloader you have. Flashing the XT1031 Boost Bootloader may be a necessary step, but if something goes wrong you have a brick on your hands.
ATTACK said:
Those are the stock activation apps that are needed if you plan to use the phone. Typically, they "go away" or are "unseen" when the device is activated.
Sent from my XT1031
Click to expand...
Click to collapse
I do still get activation alerts on my other ones but they are not intrusive and they can be disabled. All of the xt1031 phones I have are on wifi only. Does that mean that they are still "activated" from before? In that case is it possible to activate these two that I have without actually buying service for them?
lost101 said:
@HardOnChairs - Apologies, I got confused between Verizon and Sprint. There are no Verizon files in the Boost Firmware, only those for Sprint.
The conversion to PagePlus includes flashing the XT1028 Bootloader - so that's still the Bootloader you have. Flashing the XT1031 Boost Bootloader may be a necessary step, but if something goes wrong you have a brick on your hands.
Click to expand...
Click to collapse
I have managed to update the bootloader of one of my devices and it actually caused some issues. The display constantly glitches. This was when I was trying to update to bootloader to work on 5.x. Do you know where I can find the original bootloader for 4.x? I never managed to find it. Is it possible to pull it off of one of my other devices? Or do you know if that zip I got has the original one?
HardOnChairs said:
I have managed to update the bootloader of one of my devices and it actually caused some issues. The display constantly glitches. This was when I was trying to update to bootloader to work on 5.x. Do you know where I can find the original bootloader for 4.x? I never managed to find it. Is it possible to pull it off of one of my other devices? Or do you know if that zip I got has the original one?
Click to expand...
Click to collapse
Be very careful with Bootloaders. You cannot go back now that you have upgraded. The display 'glitch' is caused by running KitKat ROM with a Lollipop Bootloader. Turn screen off once to stop it.
lost101 said:
Be very careful with Bootloaders. You cannot go back now that you have upgraded. The display 'glitch' is caused by running KitKat ROM with a Lollipop Bootloader. Turn screen off once to stop it.
Click to expand...
Click to collapse
I see. Well that aside, thats a different phone altogether, is it possible for me to check which bootloader these new phones have? And if they are on the 1028, is it possible for me to go back to the 1031 KK version?
HardOnChairs said:
I see. Well that aside, thats a different phone altogether, is it possible for me to check which bootloader these new phones have? And if they are on the 1028, is it possible for me to go back to the 1031 KK version?
Click to expand...
Click to collapse
Check the Fastboot screen:
i) The 'hardware' way.
a) Unplug the USB cable and power off the phone.
b) Press and hold 'Volume down' then power on the phone.
c) Connect USB cable to your computer.
ii) The 'software' way.
a) Enable developer mode on the Moto G (Settings-> 'About Phone'. Tap 7 times on 'Build Number')
b) Enable USB debugging. (Settings -> 'Developer options' -> 'USB Debugging' -> check)
c) Connect phone to computer via USB, you should see a new ADB device detected and drivers installed.
d) Open Command Prompt or Terminal, navigate to the Firmware / ADB folder (i.e CD C:\motog_firmware ) and type:
Code:
adb reboot-bootloader
I don't know if you can safely flash the XT1031 KitKat Bootloader now that the phone has been converted to XT1028 - but it's likely considering that's the original Model of the phone.
The fastboot screen says
41.13 (sha-7dc8e78, 2014-06-16 16:33:29)
Click to expand...
Click to collapse
HardOnChairs said:
The fastboot screen says
Click to expand...
Click to collapse
v41.13 is KitKat, v41.18 is Lollipop.
lost101 said:
v41.13 is KitKat, v41.18 is Lollipop.
Click to expand...
Click to collapse
So I should try reflashing motoboot.img? Is there a way to be sure that it is KK?
HardOnChairs said:
So I should try reflashing motoboot.img? Is there a way to be sure that it is KK?
Click to expand...
Click to collapse
To be sure what is KitKat? v41.13 is 100% not a Lollipop Bootloader.
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!
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