Database Develop

OTA Disabled when using Cyanogen????

Hello all...
I just read about Android 2.2 Froyo that is scheduled to come out sometime within the next few months. What I am wondering is will I get the OTA update pushed to my phone from Google and will I be able to update?
I am running CyanogenMod 5.0.6-N1 on my Nexus One.
I apologize if this seems like a dumb question but I am a newbie to all this.

OTA will be gone after rooting, but the update will still be available for root users to be applied through recovery.
It might even leak to root users sooner as was done in the past
Sent from my Nexus One using the XDA mobile application powered by Tapatalk

Hey KnightMAREcrow...
Thanks for the reply.
But I don't understand what you mean by the update will still be available for root users to be applied through recovery. Huh?
Again sorry if this is a stupid question but I'm learning all this as I go.

afigs15 said:
Hey KnightMAREcrow...
Thanks for the reply.
But I don't understand what you mean by the update will still be available for root users to be applied through recovery. Huh?
Again sorry if this is a stupid question but I'm learning all this as I go.
Click to expand...
Click to collapse
If you have rooted your phone (which you have to install cyan), you will need to put back stock recovery and stock rom in order to successfully install the OTA. What Knight said was that, usually updates such as Froyo/2.2 will be out for rooted users like you through Cyan or other Roms, so you do not have to install stock rom/rec. Just wait it Out!

Ohhhhh ok so the next Cyanogen Update should incorporate all the features that will come with Froyo....GOT IT!!!!
Thanks for the lesson...much appreciated!

Even though you aren't getting a notification about the OTA - rooted users will still be able to download a .zip and flash it through recovery just like a custom ROM. This version specifically though will not be the one Google released, I believe they will change things to in order to make it usable by us rooted users.
I don't know really though, but it looks like that is what happened with the previous OTA. Cyanogen will integrate Froyo's features into his ROM regardless, so I guess it really doesn't matter.

Cm7 risk of ota upgrade?

I assume there's no risk of getting the ota upgrade because its so far from stock, but still is there a risk of getting the ota and messing things up when running cm7?
Sent from my ADR6300 using XDA Premium App

you are not in danger of B&N's OTA updates if you're on anything that's not the stock rom.

Positive with that? That's what I though too.
Thanks
Sent from my ADR6300 using XDA Premium App

Yeah, no risk of it. the OTA is built into the Stock OS and without the stock OS there, there's no way for it to communicate with it.

JLCollier2005 said:
Yeah, no risk of it. the OTA is built into the Stock OS and without the stock OS there, there's no way for it to communicate with it.
Click to expand...
Click to collapse
Not entirely true. The ROM you are running must be specifically built to reject the OTA upgrades. CyanogenMod does this with "FOTAKill.apk" app in your /system/app/ directory. Other 3rd-party ROMs usually do something similar.

Chahk said:
Not entirely true. The ROM you are running must be specifically built to reject the OTA upgrades. CyanogenMod does this with "FOTAKill.apk" app in your /system/app/ directory. Other 3rd-party ROMs usually do something similar.
Click to expand...
Click to collapse
I am sorry but this is just not true. A Nook Color running CM7 has no earthly way to look for OTA updates. OTA updates must be originated by the device...they are not originated by the B&N servers. Otherwise, you would have us believe that the B&N servers are constantly scouring the global internet, looking for stock or modified Nook Colors, and trying to force push updates (which amount to a total re-install of the OS in the case of CM7). Even as absurd as that sounds, they would also have no way of recognizing a Nook Color running CM7 - all software vestiges that might identify the device as a Nook Color were removed once the internal memory was flashed and replaced with CM7. Additionally, the authors of CM7 would never build in anything that would have the device look for OTA updates from the B&N servers...that would really just completly defeat the purpose of the project. It is just not possible for a Nook Color running CM7 to get an offical B&N OTA update and reflash your device back to stock.
I have no idea what the FOTAkill app is for, but it not for this. Perhaps it might be a remnant of whatever device the original code for CM7 was pulled from...to disable the desire for that original device to look for OTA updates. Or, it might be something completely unrelated to OTA updates and just happen to have a similar name.

Original post taken back. Wrong forum. Oops :–)
Sent from my LogicPD Zoom2 using XDA App

Update 5.8.894

I am running 5.8.894 and .. as far as I can tell, I am the only one. I have seen 5.7.894, and 7.893 .. but I am 5.8.894.
I have two questions.
1) What is the .8? Is it kernel?
2) Am I one of the first, or are my searching skills just way off.
A couple observations as well. I did a full stock restore, applied the 4EVER Root, did a cheesecake to the staging servers of the big M, applied it and I still have root.
Camera is WAAAAAYYYYY Faster too. Hopefully it fixes the radios issues as well and the application vanishing.

So you went out and grabbed this OTA version?
Sounds like it might be the "official" Moto soak test OTA. That is allegedly (It IS Moto after all) about to or already circulating to testers.
How is it running? Impact on battery usage?
Thanks,
RMD

I just installed so I don't really have anything to say about it yet.
So you're saying this is the "official" OTA that I picked up?

I'm guessing that it MAY BE THE OFFICIAL OTA. No way of knowing for certain yet.
Since you grabbed it off an "M" server, that would be my guess.
I haven't yet seen any reports of folks involved in the soak test reporting what version the OTA results in on their handsets.
Keep us posted.
Thanks,
RMD

blocatan said:
I am running 5.8.894 and .. as far as I can tell, I am the only one. I have seen 5.7.894, and 7.893 .. but I am 5.8.894.
I have two questions.
1) What is the .8? Is it kernel?
2) Am I one of the first, or are my searching skills just way off.
A couple observations as well. I did a full stock restore, applied the 4EVER Root, did a cheesecake to the staging servers of the big M, applied it and I still have root.
Camera is WAAAAAYYYYY Faster too. Hopefully it fixes the radios issues as well and the application vanishing.
Click to expand...
Click to collapse
was this update pushed to your phone or did you manually download it from somewhere and install it yourself?

I think he snagged it using cheesecake off a server at Moto.
RMD

rduckwor said:
I think he snagged it using cheesecake off a server at Moto.
RMD
Click to expand...
Click to collapse
Thats a big 10-FOR

yeah my bad, sorry for not reading your original post more carefully

I think it's interesting that this update doesn't block perma root when the first .894 update did. Does this mean Motorola is taking steps in the right direction or is it something as simple as they forgot to put it in this version? Who knows, I'm hoping it's the former though.

I was thinking the very same thing? Moto grows a heart? Or maybe a brain?
RMD

which server from cheesecake?
im going crazy trying to look for it :/

qubanaso said:
which server from cheesecake?
im going crazy trying to look for it :/
Click to expand...
Click to collapse
master-sdc100.blurdev.com under Staging is where I picked it up.

Did you update from stock or from 5.7.893? I'm checking the servers via cheesecake and I cant seem to find it (im on 5.7.893).

P3 has tweeted not to take it that it patches root.

Keep us posted if u have data issues!
Sent from my DROID BIONIC using Tapatalk

were u using wifi or on data?
Sent from my DROID BIONIC using xda premium

So i got tired of waiting for a response so I decided to follow the OPs instructions....I wiped my system back to 886, rooted/forever rooted and launched cheesecake. I saw 5.8.894 on master-sdc100.blurdev.com and attempted to apply the update.
I got an error that the update failed to go through.

yea i had the same problem trying to update with the forever root im currently running 5.5.893
Sent from my DROID BIONIC using xda premium

Haven't seen the update in cheesecake app. Would like to know if anything is different
Sent from my DROID BIONIC using Tapatalk

So i tried to go back to stock without root and apply the update and it still fails on the validation. I guess this means we are off the upgrade path till a leaked fxz appears.
edit: to find the update you need to have a stock system image, for it to install it looks like you need to be 100% stock (bootloader/kernel/radios as well as system).

Anyone port the ICS leak's radios and kernel yet?

I know there were 2 leaks of ICS for the phone, but has anyone been able to update the ICS ROMs in the threads to use the new kernel and radios? There's still some data issues and we're using a GB kernel
EDIT: i meant leaks, stupid typo

The kernel is based on GB because of the locked bootloader. At least that's how I am to understand it. In other words I think that the custom ROMs can be improved using the leaked ROMs but they'll still have to remain based on the GB kernel. Unless you update your stock system to ICS that is. I think the biggest thing devs should focus on right now is a way to safely upgrade to ICS where downgrading is possible in order to stay on Verizons official upgrade path.
As it stands, the OTA will look for GB 219 when upgrading so those early adopters won't be able to get future upgrades. Unless devs find a way to downgrade or trick the update that is.
Everything I've said could be wrong however this is how I have come to understand it.
Sent from my DROID4 using XDA

Given that we have the fastboot files can't we just wipe and flash that to downgrade?
Sent from my DROID4 using XDA

azrael293 said:
Given that we have the fastboot files can't we just wipe and flash that to downgrade?
Sent from my DROID4 using XDA
Click to expand...
Click to collapse
No, this results in a brick. Fastboot refuses to flash older partitions over new ones.
Sent from my XT894 using xda premium

flamefangahs said:
The kernel is based on GB because of the locked bootloader. At least that's how I am to understand it. In other words I think that the custom ROMs can be improved using the leaked ROMs but they'll still have to remain based on the GB kernel. Unless you update your stock system to ICS that is. I think the biggest thing devs should focus on right now is a way to safely upgrade to ICS where downgrading is possible in order to stay on Verizons official upgrade path.
Click to expand...
Click to collapse
This is why you need kexec - you can load the ICS kernel dynamically, without corrupting your GB install.
Sent from my DROID4 using Tapatalk

highlandsun said:
This is why you need kexec - you can load the ICS kernel dynamically, without corrupting your GB install.
Sent from my DROID4 using Tapatalk
Click to expand...
Click to collapse
Actually, upgrading to ICS leak is probably the way to go. We can now upgrade from leak 200 to 206, giving us the ability to stay on the upgrade path. Since the XDA forums are dead for the Droid 4, I suggest everyone keep up at droidforums.
Here are the instructions for upgrading from leak 200 to 206:
http://www.droidforums.net/forum/droid-4-roms/209619-get-unstuck-ics-leak-200-aka-upgrading-200-206-instructions.html
Also, I believe Hashcode is working on bringing Safestrap 2.0 to the new ICS leak based on the new kernel, and will be working on getting our ROMs on the new kernel as well.

rumgool said:
Since the XDA forums are dead for the Droid 4, I suggest everyone keep up at droidforums.
Click to expand...
Click to collapse
droidforums is about as dead for the Droid 4 as is XDA. I am really surprised how little interest people have in this phone. I guess I am one of the few that still loves physical keyboards. Only drawback on this phone is the non-removable battery. Otherwise it is rock solid. Had the original Tilt, then TP and TP2. Had the G2 on T-mobile, but reception on that phone was not good and T-mobile Network in the US sucks.

GermanGuy said:
droidforums is about as dead for the Droid 4 as is XDA.
Click to expand...
Click to collapse
This is true, I was just mentioning since most of the recent information regarding the ICS leak has been on droidforums so checking it out would fill everyone in on whats going on. Because basically development for the GB kernel is probably going to come to a halt and future development will be based on the new ICS kernel, including the existing AOSP ROMs.

wait, the 206 version keeps you on the upgrade path?

dewhashish said:
wait, the 206 version keeps you on the upgrade path?
Click to expand...
Click to collapse
No, but 206 was supposed to require 219 as 200 did and the official one will and people have found ways around it.
Sent from my XT894 using xda premium

I have Hashcode's stuff running on my kindle fire. We will all be in for a treat once he starts focusing on D4. He's done really really good work on the kindle.

dewhashish said:
I know there were 2 leaks of ICS for the phone, but has anyone been able to update the ICS ROMs in the threads to use the new kernel and radios? There's still some data issues and we're using a GB kernel
EDIT: i meant leaks, stupid typo
Click to expand...
Click to collapse
They won't be able to do so. What they will be able to do is make their builds work off/with the new kernel/radios flashed by the leak.
So Hashcode will have two builds.
1) - works on phones running the current stock GB kernel.
2) - works on phones running the leaked ICS kernel.
There is still a locked bootloader so you can't flash unsigned kernels/boot.img. For the leaked "system" files to help you need the ICS kernel. The only way to get the ICS kernel is to flash the leak.
So the leaks are great news for people wanting an AOKP or CM9 build running fully functional....on their leak installed phones. Not much help for those who do not want to flash the leak.

I'll definitely flash the leak once root has been released for 4.0.4 (in case OTA rootkeeper doesn't work) and hashcode releases safestrap 2.0 for the leak.

I'm presently running Hashcode and the rest of the STS Dev Team's CM9 release with modifications for the ICS kernel leak on my D4 that has been flashed to the .206 leak; I just pulled their work from GitHub and compiled it myself with a few little tweaks.
So far it's working great, face unlock and the camera is working perfectly and GSM/WDCMA performance is awesome, I don't seem to have the problem of under-reported GSM signal like in the stock MotoBlur leak.
(Note that I'm in Canada and using Bell Mobility, not in the US on Verizon so I can't say if LTE is functioning properly).
I just flashed it with Safestrap v1.09 for the D4; a little tricky since the bootmenu doesn't accept the Menu/Search softkey input to allow you to enter Safestrap, so I had to boot in BP Tools mode to force loading up the Safestrap Recovery. I made some additional tweaks to the build.prop file as well but am really impressed.
Won't be long before Hashcode puts up an official release, but I definitely recommend trying it out if you're up for it. If Hashcode doesn't mind, I could share a .zip of the build I made if anyone out there is interested.
Sent from my XT894 using xda premium

Rick#2 said:
I'm presently running Hashcode and the rest of the STS Dev Team's CM9 release with modifications for the ICS kernel leak on my D4 that has been flashed to the .206 leak; I just pulled their work from GitHub and compiled it myself with a few little tweaks.
Click to expand...
Click to collapse
Do you think you create a guide or go into more detail how you did this? I'm not quite sure what their git is.
Sent from my XT894 using xda premium

Rick#2 said:
...
I just flashed it with Safestrap v1.09 for the D4; a little tricky since the bootmenu doesn't accept the Menu/Search softkey input to allow you to enter Safestrap, so I had to boot in BP Tools mode to force loading up the Safestrap Recovery. I made some additional tweaks to the build.prop file as well but am really impressed.
...
Click to expand...
Click to collapse
This is what I'm trying to fix right now. Seems like the menu/home/search/back buttons are handled as part of the touchscreen. So the new Safestrap has to handle looking for virtual buttons.
Sent from my Amazon Kindle Fire using Tapatalk 2

Hashcode said:
This is what I'm trying to fix right now. Seems like the menu/home/search/back buttons are handled as part of the touchscreen. So the new Safestrap has to handle looking for virtual buttons.
Sent from my Amazon Kindle Fire using Tapatalk 2
Click to expand...
Click to collapse
If you are making good headway, then disregard this. But you could use a scheme similar to FireFireFire for the er, Kindle Fire
Either use a physical button (a return to the old hold the X from the D1, perhaps?) or a few taps to the screen?

podspi said:
If you are making good headway, then disregard this. But you could use a scheme similar to FireFireFire for the er, Kindle Fire
Either use a physical button (a return to the old hold the X from the D1, perhaps?) or a few taps to the screen?
Click to expand...
Click to collapse
Right now, I'm treating the front buttons like they are a special portion of the touch screen (basically any touch past 960 pixels down is considered the "button row", and then I divided the width up into 4 spots for button presses: menu, home, back and search respectively. (This is in the recovery itself as well as the splashscreen which triggers off of menu)
If that fails, Ill just use hard keys for D4's Safestrap temporarily.
Sent from my DROID4 using Tapatalk 2

..or maybe the volume buttons (I bet it requires less modification than implementing support for the digitizer)

I just put up an updated Droid4 2.00 Safestrap for use w/ the new MotoICS leaks:
http://forum.xda-developers.com/showthread.php?t=1688610
BE SURE TO MAKE AN INITIAL BACKUP OF NON-SAFE SYSTEM BEFORE YOU DO ANYTHING.
You will use the "System" backup to restore back to stock .206 to update later.
I have the D4 CM9 / AOKP builds for the MotoICS leaks almost ready and I'll post those soon.

ICS Leak Flash Question

I posted these questions earlier in the Q+A section and figure this is a better place for them.....
So I've got my 4th Bionic en route due to pesky data connection issues and no GPS. I'm wondering if I should flash the .232 ICS build. A couple questions arise if I may:
- Is it easily rootable? Running .905 stock root presently on my old Bionic. New one I'm sure will have .905 obviously stock and unmessed with.
- Does installing a leaked version make it any more difficult to install the official version at its release? I'm thinking it would be a good opportunity to work bugs out of pertinent apps and familiarize myself with the new version.
- Should I root the .905 before flashing the ICS? Does that matter? I'm thinking it'd be lost anyways on the flash up. And the root of the external (not sdcard, sdcard-ext) SD I'm assuming is where I place the leaked ICS file?
I love these forums as they minimize the knowledge gap between people like me and experts!
Sent from my DROID BIONIC using xda app-developers app

dmullen1373 said:
I posted these questions earlier in the Q+A section and figure this is a better place for them.....
So I've got my 4th Bionic en route due to pesky data connection issues and no GPS. I'm wondering if I should flash the .232 ICS build. A couple questions arise if I may:
- Is it easily rootable? Running .905 stock root presently on my old Bionic. New one I'm sure will have .905 obviously stock and unmessed with.
- Does installing a leaked version make it any more difficult to install the official version at its release? I'm thinking it would be a good opportunity to work bugs out of pertinent apps and familiarize myself with the new version.
- Should I root the .905 before flashing the ICS? Does that matter? I'm thinking it'd be lost anyways on the flash up. And the root of the external (not sdcard, sdcard-ext) SD I'm assuming is where I place the leaked ICS file?
I love these forums as they minimize the knowledge gap between people like me and experts!
Sent from my DROID BIONIC using xda app-developers app
Click to expand...
Click to collapse
From everything I hear, .232 should fix your data connection. It is quite easy to update to it, you just have to put the proper update file onto your external sd card and boot into stock recovery and install it. It is also very easy to root, assuming you have access to a computer running windows. The utility to root it is called razrs_edge and is easy enough to find and download. You will lose root on the upgrade, so it's probably just as easy to wait until after the update to root it. There is also a utility available which will let you downgrade to .905 and apply the new update without losing your data when the time comes for the official update. That can be found here http://www.droidforums.net/forum/motorola-droid-bionic/214902-downgrade-902-no-app-data-loss.html Actually, that utility can probably used to upgrade and root the phone even if you're starting on .905. Also, .232 is probably your best bet right now, as .235 is built so you can't go back to anything before it properly.
Good luck!

What about the update to the official release? Would I just be able to OTA to that, providing I defrost any bloat apps Verizon so kindly includes?
And one more quick one. Can I do that flash to .232 right now on my stock, partially frozen and rooted .905 rom without losing any apps or data? Sounds way too good to be true to me!
Thanks for your time too, dude. Totally got it!
Sent from my DROID BIONIC using xda app-developers app

dmullen1373 said:
What about the update to the official release? Would I just be able to OTA to that, providing I defrost any bloat apps Verizon so kindly includes?
Thanks for your time too, dude. Totally got it!
Sent from my DROID BIONIC using xda app-developers app
Click to expand...
Click to collapse
You can't directly update to the OTA, but that's what the utility which I linked in my previous reply is for. It will let you temporarily downgrade to .905 and allow you to apply the OTA. The person who maintains it does a really good job and keeps it up to date with all the new files when they're released.

You're the man dude thanks!
Sent from my DROID BIONIC using xda app-developers app

dmullen1373 said:
You're the man dude thanks!
Sent from my DROID BIONIC using xda app-developers app
Click to expand...
Click to collapse
If you've got an account on droidforums, make sure to thank Samuri_HL, he's the one who makes things so easy to use.

OK so I've one more question. If I wanted to install it now on my bionic with the stock rooted .905, can I just download the ICS update and install while preserving apps+data?
Sent from my DROID BIONIC using xda app-developers app

dmullen1373 said:
OK so I've one more question. If I wanted to install it now on my bionic with the stock rooted .905, can I just download the ICS update and install while preserving apps+data?
Sent from my DROID BIONIC using xda app-developers app
Click to expand...
Click to collapse
As long as you're stock, the upgrade should work fine and shouldn't affect your apps+data. You will lose root (I believe) and need to re-root afterwards though.

One more question.....
OK, so I've managed to get .232 up and running. I haven't rooted it, and truly don't see the point at least at this point because I can just disable the VZ apps that I don't need (namely, all of them.) So, now that I'm on this build, let's say they release the final version tomorrow...what is going to need to happen to update to the final version? I've truly scoured through all of these forums and can't quite figure it out. Will it just be as simple as the .232 flash? I mean is it worth going to .235 on my en route Bionic and loading all of my apps and investing the hours required in getting it perfect? Or will it all just be one waste of time? I know that the final release will be an OTA, so I'm assuming that .905 will need to be in the mix at some point hence the confusion....
Kudos to all who care to help thee noobs around here!!!

dmullen1373 said:
OK, so I've managed to get .232 up and running. I haven't rooted it, and truly don't see the point at least at this point because I can just disable the VZ apps that I don't need (namely, all of them.) So, now that I'm on this build, let's say they release the final version tomorrow...what is going to need to happen to update to the final version? I've truly scoured through all of these forums and can't quite figure it out. Will it just be as simple as the .232 flash? I mean is it worth going to .235 on my en route Bionic and loading all of my apps and investing the hours required in getting it perfect? Or will it all just be one waste of time? I know that the final release will be an OTA, so I'm assuming that .905 will need to be in the mix at some point hence the confusion....
Kudos to all who care to help thee noobs around here!!!
Click to expand...
Click to collapse
You will need to flash the .905 fxz file in order to receive the OTA. There are a couple ways of doing that. The most failsafe way would be to do it using RSD Lite, however that will wipe all of your data and basically return your phone to a like-new state. The other main way is to use SamuriHL's House of Bionic program/script. It uses a modified version of the fxz file that will not wipe your data. You can use it to return to .905 and install the OTA in the normal way, by checking for updates and letting it install once it is available. You can also use it if you download the OTA when it is released and basically do it the same way you updated to .232. When the OTA is released, I'm sure he'll put together a new version of HoB that includes it, so that the whole process is fairly well automated. There's no saying when exactly the OTA will be ready, but for now just enjoy your ice cream sandwich.
When I mention that it will not wipe your data, that means that all of your apps and whatnot will remain intact. In any case, I don't recommend updating to .235, I have it and can't tell much difference between that and the .232 leak, and the .232 leak has a safe route back to stock, whereas .235 doesn't, so it's definitely not worth the risk. If you're happy with it without rooting, then by all means keep it that way, rooting means it's just easier to mess things up.