Database Develop

[Q] Stop Android from updating to 2.2

Is there a way to stop my Droid from updating OTA to FroYo? I have flashed my Droid over to Cricket and have Bugless Beast v0.4 installed, and now since the 2.2 OTA update has been released I get a constant notification that the update is available. The only options I get are to install now or to install later, but what if I don't want to install it all and just get rid of the pesky notification that keeps popping up every so often after I press install later. I already have 2.2 on my system with Bugless Beast so I'm not really missing out on anything. I don't want to update and have to reroot, reinstall Bugless Beast, and reflash my Droid to Cricket again. I'm happy where my system is at

If you have a custom recovery, then as soon as you reboot into the installation your phone thinks that you've accepted, but the custom recovery blocks the installation and you stay on BB.

What do you mean by reboot into installation?
I've booted into clockwork recovery and then restarted the phone, but nothing seemed to change. Is that what you meant to do?

Flash SPRecovery. Then select "install now". It will send a notification that it has been installed on your phone to the servers that send out the OTA but SPRecovery will block the installation of it onto your phone, thus stopping the notifications of an update and keeping you on BB v.04 w/ Cricket. You can flash back to CW Recovery if you want to afterwards.
Sent from my Droid using XDA App

Im also running BB.04 and got the OTA notification today. Glad I found this thread because I was starting to get worried. I clicked 'install now', rebooted and so far no notification and I am still on BB.04. Woot!

Thank you for this!
Running BB 0.4. I saw the verizon 2.2 Froyo upgrade this morning, and for a second I was psyched verizon finally pushed it out... then I was a little worried about what was going to happen to mine since it was rooted and running a 2.2 Rom I was already happy with. Just like this thread says, I clicked install, and the phone rebooted right back up to my BB 0.4 without any issues.
I'd hate to say I'm a leech, but you guys have so much information here, and I cannot stop reading lol. I commend everyone one of you Devs for all the work you do!
Thank you again,
-Dano

Yup, it worked perfectly! Thank you!

Interesting. I was able to block it the first time but it popped up again. Anyone know why? Maybe there is another update to the 2.2 OTA update?

I was having the same issue with the ota update until I came across this:
http://www.peteralfonso.com/2010/08/how-to-stop-ota-notifications-on.html#more
it says it is for Buggles rom but I am using a different rom and it worked just fine

I had received this notification about four times before it recognized that I'm updated without rebooting the phone for it to be blocked. Nothing else had to be done except for saying yes.

stephen730 said:
whatchoo mean able to block it? You mean you clicked install later? Or you let it run and it goes away?
If you let it run/fail it will just come back again a day later, a week later, next time you reboot, next time you come out of screen off, etc... Its done it to me and it sucks cause it won't go away number 1, and number 2, i hate to keep rebooting to fail and possibly missing calls/texts... especially when you first wake up and the message is there like a nagscreen or advert.
Click to expand...
Click to collapse
I clicked install now and my recovery image blocks the installation when rebooted. It shows the Android guy with the exclamtion point but it doesnt finish the install. Reboot then im back to the way I was. Im running BBv.4 btw. I havent got another prompt yet.

[Q] Moto X Not Booting after trying to root PLEASE HELP

I just got my Moto X 2014 Pure Edition in the mail yesterday and now I've gone and tried to root it.
I had already unlocked the bootloader and then being giddy I installed android 5 since I wanted to try it out. From here, I messed up. I tried to root it using the Superboot method. Unfortunately, I didn't realize this was for the 4.4.4 build.
After flashing the image, I was able to get back into the OS, but I wasn't able to install apps or get to the home screen. I could still browse still open chrome windows, but I couldn't get to home. Next, I tried CF Auto Root, as that was built for 5.0. Executed just fine, but when I got back into the phone, I kept having the same problem. Now when I boot, It gets past the moto animations and then sits on the moto logo that looks like water. It just stays there.
If I try to turn off the phone, it just repeats this. If I put it into fastboot mode, it can act in there just fine. So I tried getting into recovery, but when I got back to the android on it's back saying "NO COMMAND.", I tried holding down up and power, just like everyone says. Doing this, though, reboots the phone normally and it goes back to the same problem as it was before!
If anyone has any suggestions, I'd really appreciate it. I'm having a mild breakdown right now

afran646 said:
I just got my Moto X 2014 Pure Edition in the mail yesterday and now I've gone and tried to root it.
I had already unlocked the bootloader and then being giddy I installed android 5 since I wanted to try it out. From here, I messed up. I tried to root it using the Superboot method. Unfortunately, I didn't realize this was for the 4.4.4 build.
After flashing the image, I was able to get back into the OS, but I wasn't able to install apps or get to the home screen. I could still browse still open chrome windows, but I couldn't get to home. Next, I tried CF Auto Root, as that was built for 5.0. Executed just fine, but when I got back into the phone, I kept having the same problem. Now when I boot, It gets past the moto animations and then sits on the moto logo that looks like water. It just stays there.
If I try to turn off the phone, it just repeats this. If I put it into fastboot mode, it can act in there just fine. So I tried getting into recovery, but when I got back to the android on it's back saying "NO COMMAND.", I tried holding down up and power, just like everyone says. Doing this, though, reboots the phone normally and it goes back to the same problem as it was before!
If anyone has any suggestions, I'd really appreciate it. I'm having a mild breakdown right now
Click to expand...
Click to collapse
Easiest thing to do is to go to:
https://accounts.motorola.com/ssoau...edirect/standalone/bootloader/recovery-images
and log in then find the right link for Moto X Pure Edition and click the "Request Firmware" link. When you get the email giving you access to the link then following the instructions for flashing it via fastboot.

crpalmer said:
Easiest thing to do is to go to:
and log in then find the right link for Moto X Pure Edition and click the "Request Firmware" link. When you get the email giving you access to the link then following the instructions for flashing it via fastboot.
Click to expand...
Click to collapse
Thank you so much for this! I had eventually found a fix through a lot of tinkering, but thank you for replying with the link for the firmware. I was looking everywhere for it!

I had the same issue. I have no idea what I did to cause it. Eventually I found a fix somewhere to fastboot into twrp recovery from the computer, and fix the file system. Then I flashed kitkat and updated from there.
Sent from my Nexus 5 using XDA Free mobile app

Recovery image or fix?
can you guys post your fixes? I am stuck with the same issue and have been waiting for over an hour for Moto to send me the recovery image. Thanks!

Xtchico..look at solartrans guide to get on lollipop. You basically have to downgrade to 4.4.4...then you'll get the 5.0 ota ..then use the tools to unlock..root and install recovery.
That's what worked for me. I was stuck on the water ripple M .
Sent from my XT1095 using XDA Free mobile app

fastercon said:
Xtchico..look at solartrans guide to get on lollipop. You basically have to downgrade to 4.4.4...then you'll get the 5.0 ota ..then use the tools to unlock..root and install recovery.
That's what worked for me. I was stuck on the water ripple M .
Sent from my XT1095 using XDA Free mobile app
Click to expand...
Click to collapse
This is exactly the guide that I used and the fix action which worked for me. Thank you sir for finding it! I'd been trying to find it to give him credit. It works wonders and I haven't had an issue since.
Rooted my phone, loaded my applications and tweaked it to my liking. Now all that's left is to activate it.

Got the 5.0.1 notification but...

Well I am surprised I received the 5.0.1 update notification but after agreeing and letting device restart, it didn't happen and device claims that is up to date and still on 5.0
Did Google retired the OTA?

Your not alone im having the same issue. My 6 is on verizon and the same issue has happened that you described. Cleared data in the frame service. Phone claims up to date...still 5.0

Darn it....
At least AT&T and Verizon respect the "direct updates form Google" advantage of the Nexus brand.

Anyone able to help?

If you've flashed a custom recovery and/or are rooted, the OTA will fail. It will just reboot without doing anything, then the OTA disappears when back in Android and autoupdate says you're up to date.
You can download the image from the Nexus factory images site, extract the system and radio images, and flash them yourself with either fastboot or Nexus Root Toolkit.
This post gave me the idea:
http://forum.xda-developers.com/showpost.php?p=57411133&postcount=75
And here's the link to the latest N6 image from Google:
https://dl.google.com/dl/android/aosp/shamu-lrx22c-factory-ff173fc6.tgz
You'll need WinRAR or similar to extract the download from Google.

It failed for me too, bone stock. Connect your phone to a charger . it reappear and I was able to update

Dxtra i have tried this and it has yet to reappear how long has it taken for you to see it repop

Same here.... Verizon/Stock Nexus 6. Mine didn't even reboot. After I chose to accept the update, screen just flashed to up-to-date. Now claiming up-to-date each time.

Strange I'm in the UK and have the exact same problem. Got a notification thru last night for the 5.0.1 update, decided to leave it until this morning and it's gone. Must be something to do with Google.....

I am bone stock and have the same issue . Last night it said there was a new update and I said ok lets do it.. It said it was going to restart and then it never restarted or nothing and says its up to date even though its on 5.0 . I am on verizon !!!

StrangeTimes said:
Dxtra i have tried this and it has yet to reappear how long has it taken for you to see it repop
Click to expand...
Click to collapse
Immediately. I guess I was lucky

I did not root/installed custom ROM neither, which boost the upset. But again, I am glad that I should not worry for update delays due the device being from a carrier's branded, and evidently I am not the only one, I will give Google the opportunity before opting for manually flash the update which that means dealing with an 20+ GB backup first.
Sent from my Nexus 6 using XDA Free mobile app

Question
Hey i was wondering, I got my OTA update last night and of course my phone is unlocked and rooted but i still attempted to download and install it. I was successful in downloading the update and my device rebooted. I shortly got the error message so i rebooted the device and when i logged back on i was still on 5.0 and the OTA notification is now gone.
My question is, since i downloaded 5.0.1 and the device rebooted in the attempt to complete the install will this now cause my phone to no longer get the 5.0.1 update notification? I plan on unrooting once i get the notification so i can go ahead and OTA and when that is completed root the phone again. Or am I now forced to flash a factory reset in order to get that OTA update again?
ideally i would prefer to wait for the OTA so i dont have to factory reset.

ATT Stock
I had this disappearing 5.01 update issue as well. I figured I'd grab the OTA and adb sideload load as I had in the past. However, I've found that I can't get the device to go into Recovery mode at all. Power and Volume+ at the robot with the red exclamation triangle yields nothing. Perhaps the reason the update didn't happen is because the update itself couldn't activate Recovery either.

gleonard3 said:
I had this disappearing 5.01 update issue as well. I figured I'd grab the OTA and adb sideload load as I had in the past. However, I've found that I can't get the device to go into Recovery mode at all. Power and Volume+ at the robot with the red exclamation triangle yields nothing. Perhaps the reason the update didn't happen is because the update itself couldn't activate Recovery either.
Click to expand...
Click to collapse
Once you're in the recovery screen, make sure you are holding the power button first, then clicking volume up. If you hit them at the same time it doesn't work.

capcanuck said:
Once you're in the recovery screen, make sure you are holding the power button first, then clicking volume up. If you hit them at the same time it doesn't work.
Click to expand...
Click to collapse
You are correct! Thanks. Reading elsewhere had it backwards. This worked. Off to update now. Thanks again.

No worries bud

capcanuck said:
Once you're in the recovery screen, make sure you are holding the power button first, then clicking volume up. If you hit them at the same time it doesn't work.
Click to expand...
Click to collapse
Do I hold down power first for a while before volume up? Its driving me crazy
Sent from my Nexus 6 using XDA Free mobile app

Do I need to be rooted to flash update? On my one plus I could download update and the go to recovery and flash it.
Tia,
Ian B

Slorks said:
Do I hold down power first for a while before volume up? Its driving me crazy
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Just for literally a second or so..

Thinking about lollipop upgrade

im pretty happy with kk, but i do want to be on 5.0, so i just wanted to make a few thing clear first.
1. if anything goes wrong with flashing a captured ota, how to restore my kk as it is now? will simply restoring a twrp backup do the trick on any stock rom?
2. where can i find the stock rom? the motorola site links arent working for me.
3. the quicksettings panel. is there a way/mod/app/ that will let me pull down quicksettings with one swipe like on cm and with gravitybox?
4.i really like to be able to customize the quicksettings, is that possible?
5. are there any bugs that seriously affect most users?
i am planning to root immediately so root only mods are fine.
im on a rooted unlocked bootloader xt1063,
thanks for your time,!

1. Just flash the stock ROM via fastboot.
2. I guess are some links on the Development section.
3. in 5.0, unfortunately not.
4. I guess no :/
5. Only a bootloop that happens with the newest versions of SuperSU (the only versions that works with 5.0), no major bugs..
Sent from my XT1063 using XDA Free mobile app

thanks for your fast response
is there a fix for said bootloop yet? can you show me a link?

Kobro said:
thanks for your fast response
is there a fix for said bootloop yet? can you show me a link?
Click to expand...
Click to collapse
When I ran into that problem I just hard reset (hold power button until it reboots) then let it run the course. After another reboot it came up to the lock screen and all was well. I have not had any issues since.
That said, I suspect if I had just left it for a few minutes without the hard reset it would have been fine. My tendency (as is the case with most people in these forums) is to be impatient, and jump the gun before things are completed.
The first reboot after installing Lollipop takes a while so don't get impatient.
I am using an XT1063.

pastorbob62 said:
When I ran into that problem I just hard reset (hold power button until it reboots) then let it run the course. After another reboot it came up to the lock screen and all was well. I have not had any issues since.
That said, I suspect if I had just left it for a few minutes without the hard reset it would have been fine. My tendency (as is the case with most people in these forums) is to be impatient, and jump the gun before things are completed.
The first reboot after installing Lollipop takes a while so don't get impatient.
I am using an XT1063.
Click to expand...
Click to collapse
lol im no noob to flashing roms and updates, i am new to lollipop
thanks so much for your info, it is very helpful.

Kobro said:
lol im no noob to flashing roms and updates, i am new to lollipop
thanks so much for your info, it is very helpful.
Click to expand...
Click to collapse
I wasn't implying you were a noob, just sharing my experience with you since you asked the question. Every device has its own quirks and idiosyncrasies. And I have seen posts from people with apparent considerable experience that displays much impatience.

Kobro said:
3. the quicksettings panel. is there a way/mod/app/ that will let me pull down quicksettings with one swipe like on cm and with gravitybox?
4.i really like to be able to customize the quicksettings, is that possible?
Click to expand...
Click to collapse
Try pulling down with two fingers instead of one- I've heard that this is the shortcut for the quick settings. (I don't have a device w/ 5 to try.) I think Google has also made the tiles in the quick settings dynamic and "smart" based on what you use most often. I tend to prefer having a static view and knowing exactly which ones are present (and in the same place!), but I won't know until I actually use it more.
I have the US GSM variant (XT1064) which came preloaded with 21.11.23. The OTA I've found only applies to 21.11.17 (the original release), and I've not had any luck downgrading. Good luck in your Lollipop quest!

Flash custom rom and enjoy lollipop

pastorbob62 said:
I wasn't implying you were a noob, just sharing my experience with you since you asked the question. Every device has its own quirks and idiosyncrasies. And I have seen posts from people with apparent considerable experience that displays much impatience.
Click to expand...
Click to collapse
your right for stating everything clearly, my bad

anomalyconcept said:
Try pulling down with two fingers instead of one- I've heard that this is the shortcut for the quick settings. (I don't have a device w/ 5 to try.) I think Google has also made the tiles in the quick settings dynamic and "smart" based on what you use most often. I tend to prefer having a static view and knowing exactly which ones are present (and in the same place!), but I won't know until I actually use it more.
I have the US GSM variant (XT1064) which came preloaded with 21.11.23. The OTA I've found only applies to 21.11.17 (the original release), and I've not had any luck downgrading. Good luck in your Lollipop quest!
Click to expand...
Click to collapse
yes that works, and has been since 4.3, on my custom rom devices it just is not so comfortable on a 5" device i was thinking more of something like pull down from right.

these responses motorola about the model xt1068
Catherine: Hi, my name is Catherine. How may I help you?
ENRICO: good morning
are to hold model xt1068, I wanted to know when will the update to Android 5
Catherine: Hi, at the moment we do not have a release date for Lollipop in Europe. It is currently going through testing before release but we are working hard to get it out as soon as possible. You can find the latest information at http://www.motorola.com/updates
ENRICO: thanks
Catherine: No problem, is there anything else that I can help you with?
ENRICO: no thanks
Catherine: Ok, have a nice day!
ENRICO:

pastorbob62 said:
When I ran into that problem I just hard reset (hold power button until it reboots) then let it run the course. After another reboot it came up to the lock screen and all was well. I have not had any issues since.
That said, I suspect if I had just left it for a few minutes without the hard reset it would have been fine. My tendency (as is the case with most people in these forums) is to be impatient, and jump the gun before things are completed.
The first reboot after installing Lollipop takes a while so don't get impatient.
I am using an XT1063.
Click to expand...
Click to collapse
just wanted to let you know, i have successfully flashed lollipop, rooted with twrp, run into the bootloop, found a solution in the general forum, (wipe cache and dalvik) and voila rooted 5.0
thanks for all your input.

Kobro said:
just wanted to let you know, i have successfully flashed lollipop, rooted with twrp, run into the bootloop, found a solution in the general forum, (wipe cache and dalvik) and voila rooted 5.0
thanks for all your input.
Click to expand...
Click to collapse
Don't need it now, but good to know should I have to reflash in the future. Thanks for the info. :good:

Bricked HTC One M7, I need serious help!

Hello everyone, I used to have an account on here years ago and I just had to create a new one for the purpose of this thread. Let me know if this type of issue has already been resolved but I have spent a great deal of time trying to locate a solution with no results. I have an older HTC One m7 I started using again to try and use the hotspot on it because I have unlimited data I needed to root it. Only reason for the hotspot is because I just moved and I am still waiting for my internet service to be hooked up on the second. Anyways, down to buisness. I made myself a developer on my device, unlocked the bootloader and installed TWRP V2.5.0.0 onto my phone. All was going well until the phone went to reboot. After it rebooted I was in the TWRP recovery menu, and I went to back up. As soon as I clicked it the phone completely froze up on that screen. And then a lock image appeared with TWRP across where the combination would go and i could still see everything in the background. Install, back up, mount, restore, settings, reboot etc. And beneath the image of the lock, which actually appears to be unlocked it says swipe to unlock and has a slider beneath it. Completely unresponsive on the screen, I cannot select anything at all. No different combinations of presses on the volume keys or power button is resetting or doing anything. I cannot even get it to turn off. I did notice, when i long press the power button the back arrow and home button flash simultaneously (on the HTC One M7 those are touch screen buttons, that are actually visible even when the device is off, but also completely unresponsive. I did notice as well that if I plug in my phone charger in the background above the menu options it shows how charged my battery is, and appears to charge when I plug it in. It is a silver, HTC One M7, AT&T version, running android 5.0.2 Thank everyone in advance, I tried to be as detailed as possible but let me know if more information is required to understand what is going on here. Thank you!

***UPDATE***
Ok everyone, issue resolved luckily since I did not get any responses on here. To anyone experiencing that same issue that I described. I let the phone die completely while it was frozen on the TWRP screen. I plugged it in while pressing down volume, and power button at same time and that allowed me to access the bootloader finally once more! From there you can select fastboot, then select reboot and everything will kick back up like normal! Just in case anyone finally stumbles across this what is a safe way to root my phone other than using TWRP? Thank you in advance!

cbmccown said:
Ok everyone, issue resolved luckily since I did not get any responses on here. To anyone experiencing that same issue that I described. I let the phone die completely while it was frozen on the TWRP screen. I plugged it in while pressing down volume, and power button at same time and that allowed me to access the bootloader finally once more! From there you can select fastboot, then select reboot and everything will kick back up like normal! Just in case anyone finally stumbles across this what is a safe way to root my phone other than using TWRP? Thank you in advance!
Click to expand...
Click to collapse
The best way to root your phone is to use the custom ROM's root manager. This is built in to cyanogenmod based roms, and doesnt require SuperSU. there is no app and it doesnt bother you about installing binaries or updating.
I always used SuperSU until I used CM.
Of all the ways to install root management, are these two the best. There is kingroot if you arent that concerned about the use of this third method.
For many the SuperSU (also installed by TWRP) is the most popular. Many will not know of the Custom ROM settings for root management and will install SuperSU over their setup. Its probably gonna be found in developer options, the root access toggle. It might be found in plain old settings though.

kruc Ire said:
The best way to root your phone is to use the custom ROM's root manager. This is built in to cyanogenmod based roms, and doesnt require SuperSU. there is no app and it doesnt bother you about installing binaries or updating.
I always used SuperSU until I used CM.
Of all the ways to install root management, are these two the best. There is kingroot if you arent that concerned about the use of this third method.
For many the SuperSU (also installed by TWRP) is the most popular. Many will not know of the Custom ROM settings for root management and will install SuperSU over their setup. Its probably gonna be found in developer options, the root access toggle. It might be found in plain old settings though.
Click to expand...
Click to collapse
Also, it always restarts if you hold the power button down for 15 *long* seconds.