Database Info

[Q] Nexus has been unusable since 5.0 OTA

As a preface, I keep my Nexus (16GB) stock/unrooted because having it down while flashing ROMs is not an option anymore. I need to the phone to work all the time, period. The irony is ridiculous.
Received the OTA from Sprint a couple of weeks ago, immediately noticed the (often-mentioned) dismal battery life and GPS hasn't been able to connect since that day. As I use GPS daily and need my phone to last for longer than 6 hours--these present full stop problems. This is in addition to the (often mentioned) stuttering/lag/freezing issues which are beyond frustrating as a heavy user. Really Google?!
Over the last week I've:
-Cleared caches multiple times
-Wiped/Factory Data Reset (3 times as it would not allow me to sign into my Google Account or sync apps)
-Spoke with Nexus Support for three hours today, which ended with 'Sorry, you'll have to call Sprint or LG'
-Tried GPS location 'fix' on XDA (didn't work)
-Been unable to send/receive SMS messages for two days
I'm beyond frustrated with this process and with Google for their lack of response in fixing widely-known 5.0 issues...on their own device. This phone is useless at the moment. What are my options? Root and roll back to KitKat? Throw this phone out of the window and go get a G3? I don't want to use a custom ROM/Recovery unless there are no other options.
Thanks for any advice-

993 said:
Over the last week I've:
-Cleared caches multiple times
-Wiped/Factory Data Reset (3 times as it would not allow me to sign into my Google Account or sync apps)
-Spoke with Nexus Support for three hours today, which ended with 'Sorry, you'll have to call Sprint or LG'
-Tried GPS location 'fix' on XDA (didn't work)
Click to expand...
Click to collapse
For the problems you're describing, you really haven't done much to solve it.
Unlock the bootloader, flash a factory image, relock the bootloader.

Why would you speak to Nexus support for 3 hours for? Waste of time

Frankly, I wanted to see if they would even acknowledge any of the issues that appear to be quite common recently with 5.0. They clearly did not, and it was relatively little effort wasted as it was through Hangouts (on a desktop though, phone forgot how to Hangout).
I have not tried to flash the bootloader, as I said I want to keep this phone as OEM as possible. Since that doesn't appear to be an option I will update when it's complete.

993 said:
I have not tried to flash the bootloader, as I said I want to keep this phone as OEM as possible. Since that doesn't appear to be an option I will update when it's complete.
Click to expand...
Click to collapse
Please read the stickies and take advantage of the knowledge base. My suggestion keeps the phone absolutely stock. It's telling that you couldn't recognize that.

I agree, just flash the stock image from fastboot.
Sent from my Nexus 5 using Tapatalk

Wakamatsu said:
Please read the stickies and take advantage of the knowledge base. My suggestion keeps the phone absolutely stock. It's telling that you couldn't recognize that.
Click to expand...
Click to collapse
That isn't what the Nexus rep said (reps have been known to be misinformed). I have read the relevant stickies and am aware of how to use this site. You didn't read my question. As I said, I would rather not flash if there are other viable options. IF this is the only workable solution thus far for people experiencing the above listed issues then OK. Thanks for your suggestion.

993 said:
That isn't what the Nexus rep said (reps have been known to be misinformed). I have read the relevant stickies and am aware of how to use this site. It is telling you didn't read my question. As I said, I would rather not flash if there are other viable options. IF this is the only workable solution thus far for people experiencing the above listed issues then OK. Thanks for your suggestion.
Click to expand...
Click to collapse
Flash the factory image. OTAs sometimes fail to implement properly. What you are describing is almost certainly that. You've already tried everything you can to fix the issues short of flashing. So flash.

You either have bad hardware, or the upgrade didn't install correctly. As others have mentioned, flashing the factory image should work.

993 said:
You didn't read my question. As I said, I would rather not flash if there are other viable options.
Click to expand...
Click to collapse
You said that you don't want to flash a custom rom. A factory image is what is installed on the Nexus by Google. Again, you're betraying a lack of knowledge on this subject.

If you wanted stablity you should of stayed on kitkat, hence why i never updated, you a os i can rely on and thats currently 4.4, as usual android builds at the start have minor issues and we wait for google to fix them.
I usually dont update till the devs can get a functioning build thats suitable for the community.
as above,
Fastboot oem unlock, flash 4.4 or 5.0 google image, relock bootloader
If he doesnt want to flash a custom rom then he should know how to flash a stock rom.
https://developers.google.com/android/nexus/images

I don't even speak to my own family for 3 hours, let alone a complete stranger lol wow

Wakamatsu said:
You said that you don't want to flash a custom rom. A factory image is what is installed on the Nexus by Google. Again, you're betraying a lack of knowledge on this subject.
Click to expand...
Click to collapse
Here's what's been done so far several times over:
Unlocked Bootloader
Installed SDK kit from Google using their walk though
Attempted ADB sideload of Google Factory images (5.0 then 4.4) from appropriate modes on CWM and TW
Attempted Fastboot (works only with CWM, no push/pull)
Multiple Full Wipes in both recoveries
Attempted ADB commands through terminal (W7 Pro - Admin)
Uninstalled, Reinstalled all recommended device driver packages, only recognizes in device manager as 'Google Nexus ADB Device' not Explorer Shell (read relevant FAQs) regardless of driver.
Used multiple USB ports/cables, rebooted PC each change in configuration
Root Toolkit 1.9.9 does not recognize through ADB
As of current, only Bootloader (unlocked) and Recovery mode work. I cannot access the SD card of the device through any means I've tried. The last that the OS booted I ensured that USB debugging was on in Settings. ADB mode in either recovery does not change device recognition on PC, nor does file system appear. System will not boot to ensure debugging setting has remained. Same issues with a laptop with no known prior driver issues.

993 said:
Attempted ADB sideload of Google Factory images (5.0 then 4.4) from appropriate modes on CWM and TW
Attempted Fastboot (works only with CWM, no push/pull)
Click to expand...
Click to collapse
You can't sideload a factory image. Fastboot commands are executed in bootloader, not recovery.

That should read that 'fastboot only responds to commands while CWM is the recovery'.
I can flash recoveries by this method from CMD but anything else (ROMS, etc) show progress but end before completion.

993 said:
That should read that 'fastboot only responds to commands while CWM is the recovery'.
I can flash recoveries by this method from CMD but anything else (ROMS, etc) show progress but end before completion.
Click to expand...
Click to collapse
Dude, you really need to read and understand the stickies before you do something bad to your phone. You are just flailing right now.
And really, all you needed to read was the install instructions on the Google factory image page.
1) Unlock bootloader
2) Unzip the factory image zip
3) Reboot in to bootloader
4) Run the flash-all script in the factory image folder.

This was the first method I tried. I have downloaded the factory image from Google several times and I get an 'unexpected end of data' message in 7zip when extracting my copies. Downloading from Google has been hit or miss with 'unknown network error' that halts the download, not sure what that could be.
I am trying to pinpoint the cause of these issues, as flashing back to factory without good images won't be possible. I understand how straightforward a factory flash should be especially with OEM tools but in my case I keep running into roadblocks.

Disable your antivirus and firewall during the download, that may help.

gee2012 said:
Disable your antivirus and firewall during the download, that may help.
Click to expand...
Click to collapse
Thanks for your suggestion. I disabled MSE + Firewall on the W7 machine and attempted to download [hammerhead-lrx21o-factory-01315e08.tgz] again from Google with the same error result, halting the download before completion.
My main machine, a Chromebook, will download the file completely however the zip cannot be moved without losing file size (downloads the entire 556.3MB, however once moved it magically becomes 417.2MB).
Further, I went to the Sprint Store today (I know) to see what the techs could do about pushing the factory image on the device. After about 30 minutes, they came back with "You should call Google". Brilliant. Now all I need is someone to suggest I call LG and the trifecta will be complete.

993 said:
Thanks for your suggestion. I disabled MSE + Firewall on the W7 machine and attempted to download [hammerhead-lrx21o-factory-01315e08.tgz] again from Google with the same error result, halting the download before completion.
My main machine, a Chromebook, will download the file completely however the zip cannot be moved without losing file size (downloads the entire 556.3MB, however once moved it magically becomes 417.2MB).
Further, I went to the Sprint Store today (I know) to see what the techs could do about pushing the factory image on the device. After about 30 minutes, they came back with "You should call Google". Brilliant. Now all I need is someone to suggest I call LG and the trifecta will be complete.
Click to expand...
Click to collapse
Try LG to see if they will help. Haha had to.
Can you not download on your phone? I'm not familiar with sending MMS but does it work forcing your phone to 1x? I'm trying to think of ideas. What all apps do you have installed?
Sent from my Nexus 5 using XDA Free mobile app

Did I just brick my OPO?

Hey everyone.
I was using a custom ROM, just to try Lollipop, and saw the OTA rolling out today.
I started Bacon Root Toolkit and returned my phone to stock, with the 4.4.4 original ROM, with the automatic download.
Then I tried updating it through the phone, but the OTA was not available for me yet. So I downloaded the file everyone was using to manually update it (cm-12.0-YNG1TAS0YL-bacon-signed.zip).
Used to same option on BRT to return to stock but this time selected the zip file I downloaded.
It started ok, with the prompt window showing the files pushed to the phone, like modem, system, cache, etc.
But then it stopped, waiting for the device.
I looked at it and the screen was turned off. I had full battery.
Waited some minutes and nothing. The phone was not recognized anymore. And it's also not turning on.
Any idea what happened and what I can do?
Thanx.

Cappelletti said:
Hey everyone.
I was using a custom ROM, just to try Lollipop, and saw the OTA rolling out today.
I started Bacon Root Toolkit and returned my phone to stock, with the 4.4.4 original ROM, with the automatic download.
Then I tried updating it through the phone, but the OTA was not available for me yet. So I downloaded the file everyone was using to manually update it (cm-12.0-YNG1TAS0YL-bacon-signed.zip).
Used to same option on BRT to return to stock but this time selected the zip file I downloaded.
It started ok, with the prompt window showing the files pushed to the phone, like modem, system, cache, etc.
But then it stopped, waiting for the device.
I looked at it and the screen was turned off. I had full battery.
Waited some minutes and nothing. The phone was not recognized anymore. And it's also not turning on.
Any idea what happened and what I can do?
Thanx.
Click to expand...
Click to collapse
You used an OTA zip to return your phone to stock? That's your problem. An OTA zip isn't a full system, it's a partial system that builds on top of the existing previous build to update the phone. So by not fully understanding what you're doing you've caused a catastrophic failure on your device.
At the moment your only hope is this:
http://forum.xda-developers.com/oneplus-one/help/guide-unbrick-oneplus-one-t3013732
If anything is going to save your phone it's that, so have a read and give it a try.
And get rid of that toolkit. I get it, toolkits might seem like they make things so much easier, but they're nothing but trouble. In this instance it's allowed you to flash an incomplete system to your phone, possibly bricking it. I'm not blaming the toolkit for this situation, this situation was caused by human error. But, if you had never used a toolkit in the first place you wouldn't have bypassed some crucial, basic, elementary knowledge. Knowledge that's needed to know what you're doing when flashing.
Toolkits allow the user to do things to their phone without actually having a knowledge of what's going on. Had you not used this toolkit in the first place you might have a better working knowledge of flashing, and you might not be in this situation right now. So yeah, maybe they seem easier, but in the long run you're better off without them. You're much better off properly learning the ins and outs of flashing and owning a modified phone.
Transmitted via Bacon

timmaaa said:
You used an OTA zip to return your phone to stock? That's your problem. An OTA zip isn't a full system, it's a partial system that builds on top of the existing previous build to update the phone.
Click to expand...
Click to collapse
The OS12 OTA zip is actually a full zip like the CM12 nightlies (the partition images are exactly the same as in the 20150411 nightly apart from boot.img & system).
You can't use the BRT to flash it though because it doesn't contain a system.img - /system is flashed using the same method as the nightlies (system.new.dat & system.transfer.list)

Spannaa said:
The OS12 OTA zip is actually a full zip like the CM12 nightlies (the partition images are exactly the same as in the 20150411 nightly apart from boot.img & system).
You can't use the BRT to flash it though because it doesn't contain a system.img - /system is flashed using the same method as the nightlies (system.new.dat & system.transfer.list)
Click to expand...
Click to collapse
Thanks man, good to know.
Transmitted via Bacon

Spannaa said:
The OS12 OTA zip is actually a full zip like the CM12 nightlies (the partition images are exactly the same as in the 20150411 nightly apart from boot.img & system).
You can't use the BRT to flash it though because it doesn't contain a system.img - /system is flashed using the same method as the nightlies (system.new.dat & system.transfer.list)
Click to expand...
Click to collapse
That's why I tried it. People were using it on TWRP.
As I had just returned the phone to stock I didn't have a modified recovery. So I used BRT.
I had flashed lots of times before. On previous phones and tablets. Found BRT just yesterday.
I'll take a look at the provided link in a moment. I'll let you guys know if it worked for me.
Thanx.

timmaaa said:
You used an OTA zip to return your phone to stock? That's your problem. An OTA zip isn't a full system, it's a partial system that builds on top of the existing previous build to update the phone. So by not fully understanding what you're doing you've caused a catastrophic failure on your device.
At the moment your only hope is this:
http://forum.xda-developers.com/oneplus-one/help/guide-unbrick-oneplus-one-t3013732
If anything is going to save your phone it's that, so have a read and give it a try.
And get rid of that toolkit. I get it, toolkits might seem like they make things so much easier, but they're nothing but trouble. In this instance it's allowed you to flash an incomplete system to your phone, possibly bricking it. I'm not blaming the toolkit for this situation, this situation was caused by human error. But, if you had never used a toolkit in the first place you wouldn't have bypassed some crucial, basic, elementary knowledge. Knowledge that's needed to know what you're doing when flashing.
Toolkits allow the user to do things to their phone without actually having a knowledge of what's going on. Had you not used this toolkit in the first place you might have a better working knowledge of flashing, and you might not be in this situation right now. So yeah, maybe they seem easier, but in the long run you're better off without them. You're much better off properly learning the ins and outs of flashing and owning a modified phone.
Transmitted via Bacon
Click to expand...
Click to collapse
I didn't try it yet, but I forgot to mention that the phone is totally dead. No lights or whatever. Neither the charging light is turning on.

Cappelletti said:
I didn't try it yet, but I forgot to mention that the phone is totally dead. No lights or whatever. Neither the charging light is turning on.
Click to expand...
Click to collapse
Numerous people who had phones which were showing absolutely no signs of life whatsoever have revived their phones using that unbrick tool I linked you to. All indications from these phones were that they were hard bricked but that tool saved them, it might take several attempts and a few hours but it's worth a try.
Transmitted via Bacon

timmaaa said:
Numerous people who had phones which were showing absolutely no signs of life whatsoever have revived their phones using that unbrick tool I linked you to. All indications from these phones were that they were hard bricked but that tool saved them, it might take several attempts and a few hours but it's worth a try.
Transmitted via Bacon
Click to expand...
Click to collapse
I'll try it, for sure.
Thanx.

timmaaa said:
You used an OTA zip to return your phone to stock? That's your problem. An OTA zip isn't a full system, it's a partial system that builds on top of the existing previous build to update the phone. So by not fully understanding what you're doing you've caused a catastrophic failure on your device.
At the moment your only hope is this:
http://forum.xda-developers.com/oneplus-one/help/guide-unbrick-oneplus-one-t3013732
If anything is going to save your phone it's that, so have a read and give it a try.
And get rid of that toolkit. I get it, toolkits might seem like they make things so much easier, but they're nothing but trouble. In this instance it's allowed you to flash an incomplete system to your phone, possibly bricking it. I'm not blaming the toolkit for this situation, this situation was caused by human error. But, if you had never used a toolkit in the first place you wouldn't have bypassed some crucial, basic, elementary knowledge. Knowledge that's needed to know what you're doing when flashing.
Toolkits allow the user to do things to their phone without actually having a knowledge of what's going on. Had you not used this toolkit in the first place you might have a better working knowledge of flashing, and you might not be in this situation right now. So yeah, maybe they seem easier, but in the long run you're better off without them. You're much better off properly learning the ins and outs of flashing and owning a modified phone.
Transmitted via Bacon
Click to expand...
Click to collapse
IT WORKED!
It was 1am yesterday when I messed up, so I decided to create the thread here and go sleep, after some troubleshooting that didn't work. I believe I'd come accross that thread you pointed, but thanks for it.
I mean... really, THANX!

Cappelletti said:
IT WORKED!
It was 1am yesterday when I messed up, so I decided to create the thread here and go sleep, after some troubleshooting that didn't work. I believe I'd come accross that thread you pointed, but thanks for it.
I mean... really, THANX! [emoji14]
Click to expand...
Click to collapse
Awesome, no worries, glad to help.
Transmitted via Bacon

Bootloop 2013 Moto G Boost Mobile XT1031 8GB

Hey guys!
To start, I want to say what an amazing place XDA is and how much information and knowledge you can get from here and how awesome the moderators are. I don't think I could ever find another amazing and/or helpful community such as those found here! Thanks to all who have helped me out with my Android issues!
Now to my issue and I apologize ahead of time if there is another thread (or related thread) found in the forum.
As the title states, I have a 2013 Motorola Moto G XT1031 Boost Mobile device. I had upgraded it to Lollipop 5.0.2 or 5.1 when it came out (I can't remember which one it was) and I had then decided to root it. I can say that I believe I was successful in rooting the device because I was able to install Supersu and use RootChecker to verify the install. Everything was going okay until i decided to research and eventually install a custom recovery and attempt to install a custom ROM. Well, let's just say that the recovery install was a bust...
In doing my research for a custom recovery, I found that TWRP had a custom recovery for my phone and apparently for my firmware via TWRP's app on the Play Store. So, I searched for my device in their in-app search for a custom recovery, downloaded it and installed it from the app. Now, my gut told me that this probably wouldn't work and that I should probably be installing a custom recovery via CLI. Nope. I didn't do this. Instead, like I said, I installed a custom recovery from the app itself. That screwed things up for me. I have no idea if it was the install, but my phone began to act incredibly strange. When in the TWRP recovery, my screen had this line that would continuously scroll from top to bottom. It wasn't a completely solid line, but it was transparent, almost like an empty thermometer glass stick was going down the screen. It was weird and not normal. I figured the phone's software was partially broken. It only did this in the TWRP recovery. Nowhere else did this happen. It was slightly annoying.
Later on I decided to install a custom ROM. Again, I did the necessary research to find out if there were any ROMs available for my phone (using XDA of course and others) and found that there were a few out there. So, I downloaded one (wish I could remember which one) and attempted to install it...keyword there. After attempting the install, my phone would not boot. Like at all. Dead. So back to the drawing board I went to try and reverse the damage. Using XDA (ironically) and a plethora of other sites, I tried to resurrect my phone and bring it back to life. After countless hours of trying and trying and trying and more and more research, I just gave up. The phone is dead. Great. $170 spent on a phone to break it a year later.
It's been roughly 4-5 months since I have attempted to redo the process and after another minor attempt, somehow I was able to remove the root completely, including the custom recovery and ROM. I don't know what the heck I did, but it worked....sort of. The phone is now stuck in a bootloop on the logo and sometimes the "bootloader has been unlocked" screen when try and factory reset the phone from the default recovery. When trying to reinstall the stock firmware, I read everywhere that I need the phone to have USB-debugging set and to have this and that. I have this and that installed on my PC, but obviously cannot enable USB-debugging which is needed for ADB and fastboot to recognize my device.
So, my question for anyone who would like to help me out is this: what are my options? Is the phone recoverable? Is there any way I can get ADB/fastboot to see my device and finally install the stock firmware on the phone? I have the proper drivers installed and ADB/fastboot are on my PC. Any help would be amazing, even if you have to tell me to junk it.

blckdragn22 said:
When trying to reinstall the stock firmware, I read everywhere that I need the phone to have USB-debugging set
Click to expand...
Click to collapse
This is incorrect, where did you read that? To reinstall the stock firmware using fastboot, you must be able to boot to the bootloader menu only.

I heard this from a few websites actually, although I could never find a situational fix for my phone. I am trying to restore back to Lollipop without a custom recovery, because within the past hour I found out TWRP was never fully removed when I tried booting into recovery from the AP Fastboot menu when doing to power+vol down option. The TWRP logo shows for about 10 seconds and then the phone tries booting normally, showing the unlocked bootloader warning.
So, yes I can boot into the bootloader menu all day long with no problems. It's just an selection I make doesn't get me anywhere. My question I guess now is: how do I go about reinstalling stock firmware via the bootloader menu. I have Minimal ADB and Fastboot installed on my PC. If I need the full ADB, I can download that. And of course I'd need the firmware, too.

You can find stock firmware images in this thread, there's also a link to an installation guide there:
http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795

_that said:
You can find stock firmware images in this thread, there's also a link to an installation guide there:
http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Click to expand...
Click to collapse
This thread had the firmware I was looking for thank you. I believe I have the flashing stock firmware process down, I hope. I'l refer to the guide if I need help. Thank you so much!

_that said:
You can find stock firmware images in this thread, there's also a link to an installation guide there:
http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Click to expand...
Click to collapse
I am trying to follow the steps listed here http://forum.xda-developers.com/showthread.php?t=2542219&page=35 and for some reason I cannot run any of the commands pertaining to the sparsechunks. This is what I get:
Is there anything you could tell me about that?
Edit: I was able to figure what the issue was when trying to write the sparsechunks. I had to insert a "." after 'sparsechunk' because that is how the file is named in the folder. However, now I am getting a new error, but it takes place on the phone screen. Every time I attempt to write a sparsechunk, it will initiate the process of doing so, but on the phone I'll get what appears to be an error saying, "Image is too large" in pink lettering. Why does this happen? Each sparsechunk file is at least 4MB less than the max-sparse-size according to the ADB and my phone, which is set to 256MB. Is there any way to change that?

blckdragn22 said:
However, now I am getting a new error, but it takes place on the phone screen. Every time I attempt to write a sparsechunk, it will initiate the process of doing so, but on the phone I'll get what appears to be an error saying, "Image is too large" in pink lettering. Why does this happen? Each sparsechunk file is at least 4MB less than the max-sparse-size according to the ADB and my phone, which is set to 256MB. Is there any way to change that?
Click to expand...
Click to collapse
Check which sparsechunk files you have and make sure you flash all of them in ascending order. If it still fails, copy/paste the contents of your command prompt window (no screenshots please).

_that said:
Check which sparsechunk files you have and make sure you flash all of them in ascending order. If it still fails, copy/paste the contents of your command prompt window (no screenshots please).
Click to expand...
Click to collapse
I will try that. There was a ...sparsechunks.0 as well apart from sparsechunks.1, sparsechunks.2 and sparsechunks.3. Shall I include that, too?
And adding the screenshot was an amateur mistake. My bad.

@_that this worked like a charm. Phone is 100% working ans usable now. Incredibly helpful. Thank you so much!

6045i usa latest 5.0.2-01001

hello i am rooted with twrp recovery installed. I was able to unroot and download the latest 5.0.2-01001 ota but im not able to install the update it would just take me to twrp recovery and stop there.?? i found the update zip and tried to flash it in twrp but it says it cant mount and failed to flash any help would be appreciated.

OTA updates will require a stock recovery. I'm in the process of getting an Idol 3 but I used to have an Idol 2 and, to return to a completely stock ROM, I had to use the Alcatel Mobile upgrade too which identified my phone, downloaded the correct firmware, and restored the phone. Prior to restoring back to stock, I had cwm and root.

Thanks for the reply I tried the software update but its not working keep saying I have the latest even when I did a full wipe. Using the latest 4.9.2 version...is there a way to make a twrp flashable ota zip from the downloaded update file in the ota cache..

lude86 said:
hello i am rooted with twrp recovery installed. I was able to unroot and download the latest 5.0.2-01001 ota but im not able to install the update it would just take me to twrp recovery and stop there.?? i found the update zip and tried to flash it in twrp but it says it cant mount and failed to flash any help would be appreciated.
Click to expand...
Click to collapse
You cannot be rooted and install a stock update...it's mentioned in several places throughout the forum. Quickest solution is to use the mobile q to restore the whole phone to factory (and in the process it will put the latest version on it). Otherwise you have to fully unroot AND if you have modified any files such as build.prop or other system files it still won't work. You CAN install with TWRP however in the process of the install it will overwrite it with stock recovery. If I had to guess I'd say you did not do the supersu FULL unroot.

famewolf said:
You cannot be rooted and install a stock update...it's mentioned in several places throughout the forum. Quickest solution is to use the mobile q to restore the whole phone to factory (and in the process it will put the latest version on it). Otherwise you have to fully unroot AND if you have modified any files such as build.prop or other system files it still won't work. You CAN install with TWRP however in the process of the install it will overwrite it with stock recovery. If I had to guess I'd say you did not do the supersu FULL unroot.
Click to expand...
Click to collapse
mobile Q is horse manure now. I ran into the same problem, whereby it says you're up to date (which it's not), even if you're running 5.0.2.7SMA-UEA1 ! I only know that one because I inadvertently flashed 5.0.2.7SMA-UEA1 today when I meant to flash 5.0.2.7SRA-UEA2.
Speaking of 5.0.2-01001, 5.0.2.7SRA-UEA2 is on longer the latest yeah... anyway we can update the firmware page? http://forum.xda-developers.com/idol-3/general/want-to-able-to-install-ota-updates-t3163745
I just tried to OTA update to 5.0.2-01001, but OTA of course does not work if TWRP is acting recovery; it just reboots to TWRP and then if you reboot system, nothing happens. Although seemingly never mentioned, we must remove TWRP (even read only TWRP) before updating OTA?

tekka-maki said:
mobile Q is horse manure now. I ran into the same problem, whereby it says you're up to date (which it's not), even if you're running 5.0.2.7SMA-UEA1 ! I only know that one because I inadvertently flashed 5.0.2.7SMA-UEA1 today when I meant to flash 5.0.2.7SRA-UEA2.
Speaking of 5.0.2-01001, 5.0.2.7SRA-UEA2 is on longer the latest yeah... anyway we can update the firmware page? http://forum.xda-developers.com/idol-3/general/want-to-able-to-install-ota-updates-t3163745
I just tried to OTA update to 5.0.2-01001, but OTA of course does not work if TWRP is acting recovery; it just reboots to TWRP and then if you reboot system, nothing happens. Although seemingly never mentioned, we must remove TWRP (even read only TWRP) before updating OTA?
Click to expand...
Click to collapse
The thread is closed. There is also no reason you NEED the most recent posted as you can flash any of them and then do an update. Mobile Q is the recommended method to re-do your phone if you can't manage to make a backup before messing with it. It has apparently worked just fine for people in this forum for every model type mentioned so the burden of proof is on your part if you can't get it to work.

famewolf said:
The thread is closed. There is also no reason you NEED the most recent posted as you can flash any of them and then do an update. Mobile Q is the recommended method to re-do your phone if you can't manage to make a backup before messing with it. It has apparently worked just fine for people in this forum for every model type mentioned so the burden of proof is on your part if you can't get it to work.
Click to expand...
Click to collapse
Why would the thread be 'closed'. OP's problem is unresolved.
'Worked' is the operative term for. Perhaps you haven't used to Mobile Q tool lately? As OP (and I) said (today), running OTA from 6045 now just reboots to TWRP, no install. Alternately, when attempting to update 6045 from Mobile Q, it just throws a funny English 'update no needed' kinduva message (pic). Incidentally, have you been to their website to find an update to this tool? Holy crap, in that respect, Mobile Q must be a virtual breakthrough for these boys! :laugh:
You're so helpful here famewolf. I've both appreciated and have been comforted by seeing your knowledge all over this subforum, since day 1. Please provide help. You tell me where this 'people' person is, and I'll wank on his boner for you. Then we have a definition of 'working fine' in stead of 'worked fine'. ? :angel:

tekka-maki said:
Why would the thread be 'closed'. OP's problem is unresolved.
'Worked' is the operative term for. Perhaps you haven't used to Mobile Q tool lately? As OP (and I) said (today), running OTA from 6045 now just reboots to TWRP, no install. Alternately, when attempting to update 6045 from Mobile Q, it just throws a funny English 'update no needed' kinduva message (pic). Incidentally, have you been to their website to find an update to this tool? Holy crap, in that respect, Mobile Q must be a virtual breakthrough for these boys! :laugh:
You're so helpful here famewolf. I've both appreciated and have been comforted by seeing your knowledge all over this subforum, since day 1. Please provide help. You tell me where this 'people' person is, and I'll wank on his boner for you. Then we have a definition of 'working fine' in stead of 'worked fine'. ? :angel:
Click to expand...
Click to collapse
The thread that is closed is the one YOU mentioned.... not the op. http://forum.xda-developers.com/idol-3/general/want-to-able-to-install-ota-updates-t3163745
I dont use mobile Q as I use Linux and they don't have a linux version. I use 3rd party roms such as AICP with the ARDE non OC rom. TWRP puts a log in /tmp...did you look at what the error message says? OTA updates will NOT apply if you have updated system files such as build.prop. Thats all I can tell you because I can't try what you are using.

famewolf said:
The thread that is closed is the one YOU mentioned.... not the op. http://forum.xda-developers.com/idol-3/general/want-to-able-to-install-ota-updates-t3163745
I dont use mobile Q as I use Linux and they don't have a linux version. I use 3rd party roms such as AICP with the ARDE non OC rom. TWRP puts a log in /tmp...did you look at what the error message says? OTA updates will NOT apply if you have updated system files such as build.prop. Thats all I can tell you because I can't try what you are using.
Click to expand...
Click to collapse
I haven't updated the build.prop, I doubt the OP has either.
'There is no greater software version available to upgrade your phone,actual version of your phone is the latest'
Hehe! Only thing that would make this funnier is if they misspelled 'version'. At least I can derive some amusement from that message and their ****ty, convoluted website.
Shame you can't help on that front, but maybe you can at least guide me on what should be normal flow of this procedure.
When one does OTA update unrooted (but with custom recovery), at the point that the phone reboots, it should not (in theory) boot into TWRP right? I would think just continue with update, and maybe that's why I would need to remove TWRP in favor of stock recovery.
It would be easier to attack it from that angle as opposed to their crappy win32 program. which they probably didn't pay the GoDaddy bill on.:laugh:
I don't even know why I'm bothering as it's just a backup phone now. I just find it ridiculous that I can get their last measly update either from Q or from device (ostensibly so long as custom recovery remains). Holy bejebus, updating Shamu is so painless (6.0.1)
---------- Post added at 08:41 PM ---------- Previous post was at 08:22 PM ----------
likely they have not updated their server side to to UEN0 from UEA2 for their craptacular tool which would explain that problem.
Curious, did you lose Band 12 with UEN0. I haven't heard anything positive from this most recent update that is giving me a headache to get to. Perhaps it's for naught. They don't even have a changelog do they. Meh... I'm going to forget about it until something notable comes along or maybe even just sell this thing while I might still get over a hundred.

tekka-maki said:
I haven't updated the build.prop, I doubt the OP has either.
'There is no greater software version available to upgrade your phone,actual version of your phone is the latest'
Hehe! Only thing that would make this funnier is if they misspelled 'version'. At least I can derive some amusement from that message and their ****ty, convoluted website.
Shame you can't help on that front, but maybe you can at least guide me on what should be normal flow of this procedure.
When one does OTA update unrooted (but with custom recovery), at the point that the phone reboots, it should not (in theory) boot into TWRP right? I would think just continue with update, and maybe that's why I would need to remove TWRP in favor of stock recovery.
It would be easier to attack it from that angle as opposed to their crappy win32 program. which they probably didn't pay the GoDaddy bill on.:laugh:
I don't even know why I'm bothering as it's just a backup phone now. I just find it ridiculous that I can get their last measly update either from Q or from device (ostensibly so long as custom recovery remains). Holy bejebus, updating Shamu is so painless (6.0.1)
---------- Post added at 08:41 PM ---------- Previous post was at 08:22 PM ----------
likely they have not updated their server side to to UEN0 from UEA2 for their craptacular tool which would explain that problem.
Curious, did you lose Band 12 with UEN0. I haven't heard anything positive from this most recent update that is giving me a headache to get to. Perhaps it's for naught. They don't even have a changelog do they. Meh... I'm going to forget about it until something notable comes along or maybe even just sell this thing while I might still get over a hundred.
Click to expand...
Click to collapse
As I mentioned here: http://forum.xda-developers.com/showpost.php?p=64967202&postcount=4 you CAN install an OTA update with twrp...it will install it just fine however at the completion of the update you will no longer HAVE twrp installed because it will have been overwritten with stock recovery. (it does that at the END) This will be apparent the NEXT time you try to load recovery. Where do you imagine the update is processed? It's processed by the recovery app...it can't be done inside the rom because files would be in use. The last version I ever ran was UER0..was not even aware UEN0 was out. As I indicated, I switched to a rom based on cyanogenmod with some features I wanted...if I was going to switch NOW I'd choose blisspop and it's the one I intend to install the next time I have to do a reinstall. I don't see why you fight on 5.02 when 5.1.1 is available in various flavors and with the ARDE NON OC Kernel is rock steady. If you made full backups of your device (ie dd images of ALL partitions using the Backupall bat file or shell script running around the forum restoring to a previous radio is as simple as reflashing the partition using fastboot commands.
The radio is stored in the "modem" partition fyi.

famewolf said:
As I mentioned here: http://forum.xda-developers.com/showpost.php?p=64967202&postcount=4 you CAN install an OTA update with twrp...it will install it just fine however at the completion of the update you will no longer HAVE twrp installed because it will have been overwritten with stock recovery. (it does that at the END) This will be apparent the NEXT time you try to load recovery. Where do you imagine the update is processed? It's processed by the recovery app...it can't be done inside the rom because files would be in use. The last version I ever ran was UER0..was not even aware UEN0 was out. As I indicated, I switched to a rom based on cyanogenmod with some features I wanted...if I was going to switch NOW I'd choose blisspop and it's the one I intend to install the next time I have to do a reinstall. I don't see why you fight on 5.02 when 5.1.1 is available in various flavors and with the ARDE NON OC Kernel is rock steady. If you made full backups of your device (ie dd images of ALL partitions using the Backupall bat file or shell script running around the forum restoring to a previous radio is as simple as reflashing the partition using fastboot commands.
The radio is stored in the "modem" partition fyi.
Click to expand...
Click to collapse
So where is the latest update to flash with twrp (good dry run for me should a decent upgrade come out that isn't UEN0)? I just went with UER0 posted on yer thread thr with all the megaupload firmwares & flash restored system & boot (after full wipe); as an aside, it took, & I still have TWRP in tact. I'm well aware of your fastboot method & orig backup of ALL partitions. Seemed like a waste of space at the time, still kinda does.
Regarding your rhetorical question, I was referencing Alcatel's w32 Q tool. It seemingly wasn't updated to be keyed in on the latest update either. No wait, it said the same 'no greater version' crap even when I restored the original 6045i US system/boot fw from twrp, lmao

tekka-maki said:
So where is the latest update to flash with twrp (good dry run for me should a decent upgrade come out that isn't UEN0)? I just went with UER0 posted on yer thread thr with all the megaupload firmwares & flash restored system & boot (after full wipe); as an aside, it took, & I still have TWRP in tact. I'm well aware of your fastboot method & orig backup of ALL partitions. Seemed like a waste of space at the time, still kinda does.
Regarding your rhetorical question, I was referencing Alcatel's w32 Q tool. It seemingly wasn't updated to be keyed in on the latest update either. No wait, it said the same 'no greater version' crap even when I restored the original 6045i US system/boot fw from twrp, lmao
Click to expand...
Click to collapse
Why are you assuming I should know where the latest and greatest update for stock should be? Updates are customized based on the rom version you are running at the time you submit a request. I've already stated I'm using a 3rd party rom and using an OS that doesn't allow me to run their software. You consider my recommendations a waste of time so I'll quit making them and continue using my perfectly working device on 5.1.1.

famewolf said:
Why are you assuming I should know where the latest and greatest update for stock should be? Updates are customized based on the rom version you are running at the time you submit a request. I've already stated I'm using a 3rd party rom and using an OS that doesn't allow me to run their software. You consider my recommendations a waste of time so I'll quit making them and continue using my perfectly working device on 5.1.1.
Click to expand...
Click to collapse
Omfg buddy, you said, '... you CAN install an OTA update with twrp' ; all I did was point out that I flashed previous updates (presumably the same way you're talking about), TWRP remained in tact afterward, & asked you to follow through with that point with, you know, the actual update in question here that defies many of your assertions. One of your recommendations is broken (Q), the other is hindsight (full backup) & last (update via TWRP) seemingly not feasible (unless someone were to submit updated /system) . Anyway it's all a moot point now since we're just measuring our junk.
I'm tickled you're running 5.1.1, as you've said repeatedly... I tried it briefly on Shamu & was happy to leave the LP quagmire all together & get to 6.0.1. Sufficed to say, there isn't anything perfect about this device or 5.1.1, which is why I'll leave as is & sell it. :good:
Thanks anyway.

Downgrade?

Hi there,
My phone has android 6.0.1 and i want it downgraded to android lollipop because ive got problems with android 6.0.1.
Im a total noob with all this stuff, so can someone please advise step by step how i can do this? I have the MOTO G 3rd Gen, SKU is "XT1541", Ram is 1GB and ROM 8GB. My current system version is 24.61.55.osprey_reteu.reteu.en.EU reteu. Build number is MPI24. 107-55. This phone will accept any phone network. Can someone please help? thanks in advance!

There are multiple threads discussing downgrading, it can be done if your device has the bootloader unlocked (which wipes data and voids the warranty)... There are some inherent dangers in doing so, some immediate and some long-term dealing with future updates which have the potential to brick the device.
What are the issues you are having, many times it is better to solve those then to downgrade.

acejavelin said:
There are multiple threads discussing downgrading, it can be done if your device has the bootloader unlocked (which wipes data and voids the warranty)... There are some inherent dangers in doing so, some immediate and some long-term dealing with future updates which have the potential to brick the device.
What are the issues you are having, many times it is better to solve those then to downgrade.
Click to expand...
Click to collapse
Some apps wont run well on android 6.0.1 such as facebook etc (personal and buisness use) and my phone generally ran better with the previous android version. The phone does not have a warranty on it anyway so that does not matter. Trust me, it really cudnt be much worse than it is atm, ive factory reset it and its just not up to standard as it was with android 5. I did have android 6.0 which i didnt like and then i got 6.0.1, which was putting ice on the cake, (in a bad way!). I am 1000% sure i want to downgrade my device. Can you help?

Ryanm353 said:
Some apps wont run well on android 6.0.1 such as facebook etc (personal and buisness use) and my phone generally ran better with the previous android version. The phone does not have a warranty on it anyway so that does not matter. Trust me, it really cudnt be much worse than it is atm, ive factory reset it and its just not up to standard as it was with android 5. I did have android 6.0 which i didnt like and then i got 6.0.1, which was putting ice on the cake, (in a bad way!). I am 1000% sure i want to downgrade my device. Can you help?
Click to expand...
Click to collapse
Not much to it... Unlock the bootloader, factory reset, then use the lollipop factory image from the factory images thread, gpt.bin will fail, just continue to flash everything all the way through. Follow the instructions in how to flash factory images, it's all done in fastboot.
Sent from my Motorola XT1575 using XDA Labs

acejavelin said:
Not much to it... Unlock the bootloader, factory reset, then use the lollipop factory image from the factory images thread, gpt.bin will fail, just continue to flash everything all the way through. Follow the instructions in how to flash factory images, it's all done in fastboot.
Sent from my Motorola XT1575 using XDA Labs
Click to expand...
Click to collapse
Thanks. But can you explain all that in more detail step by step? I need clear instructions on how to do all that as ive literally no idea about anything.

Ryanm353 said:
Thanks. But can you explain all that in more detail step by step? I need clear instructions on how to do all that as ive literally no idea about anything.
Click to expand...
Click to collapse
No offense, but this is not something to be taken lightly... there are many steps.
First, backup all your data... it will be lost.
Start by reading the first few posts in this thread... This will give the basics of what is needed to be done, what tools you need, how to do it, and the factory firmware images (you will need the correct one for your device, all the ones available are in this thread.
Next, read the first two posts in this thread... this is the instructions in detail of exactly how to flash a firmware image. Pay attention to the warnings and follow the linked threads with more information and make sure you understand all of it.
Once you have read and understand this part, you need to get fastboot working... this tool is essential to making all this work. Both of the threads I mentioned above have links to the drivers and Minimal ADB & Fastboot you will need. Install them and make sure they are working.
Now you can unlock the bootloader, this will wipe all data on your device. The instructions and process are done directly with Moto here.
Once you have unlocked the bootloader, reboot and start the bootloader and follow the instructions in the threads above, noting that the part where enter the command "fastboot flash partition gpt.bin" will likely fail because you are downgrading, but no other pieces should fail, if they do enter them again (radios are known to need to be done 2-3 times sometimes before taking), and continue all the way to the end. Pay attention to the number of sparcechunks in your image, it can will vary and you need to flash all pieces in order for your device, there could be anywhere from 5-9 pieces.
Keep a log of everything, it is much easier to tell what happened if something goes wrong by looking at the terminal log (scroll back of the terminal window) than just guessing.
TBH... I am not endorsing this method, but it generally does work, and although it is difficult to brick the Moto G 2015 it is not impossible. After you are done, you will need to root the device and freeze the updater service so you are not constantly prompted to update, and taking an OTA update can be problematic since your bootloader and/or partition table will not match the rest of the ROM correctly.
Personally I think since you have to unlock the bootloader anyway, you are probably better off just looking for a custom ROM like CM13, Resurrection Remix, or something like that since there are lots of rock solid Marshmallow aftermarket ROMs. Or if you are dead set on Lollipop, using CyanogenMod 12.1 instead of downgrading.
I know there is a downgrade utility out there, and not to take away from the developers work but I would suggest avoiding it.