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.

No stock rooted 4.2.2 rom?

I see some custom 4.2.2 Roms out, just no stock Roms yet.
My question is why not? With so many of us trying to get 4.2.2.
Sent from my Nexus 7 using Tapatalk 2

If you are in XDA u should know how to install OTA. Links are provided.
Sent from my Nexus 7 using Tapatalk 2

Jack Barrett said:
If you are in XDA u should know how to install OTA. Links are provided.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
This, a thousandfold. If you can't do this yourself - meaning you choose to not learn how to do it yourself, more often than not, and expect people to hold your hand and just fulfill the GIMME GIMME GIMME nature - then why bother, stick with stock and be done with it.
Took me what, 5 minutes to do a clean install of 4.2.1, root it, install CWM, use CWM to install the 4.2.2 update, and remained rooted.
Is it really so tough to learn how to do some things yourself? I wonder...

br0adband said:
This, a thousandfold. If you can't do this yourself - meaning you choose to not learn how to do it yourself, more often than not, and expect people to hold your hand and just fulfill the GIMME GIMME GIMME nature - then why bother, stick with stock and be done with it.
Took me what, 5 minutes to do a clean install of 4.2.1, root it, install CWM, use CWM to install the 4.2.2 update, and remained rooted.
Is it really so tough to learn how to do some things yourself? I wonder...
Click to expand...
Click to collapse
Where are you getting a clean 4.2.1 install?

I restored 4.2.1 factory image, and got the message to upgrade in minutes. After that I managed to root with the usual method. Same adb commands, recovery and SU is working as in 4.2.1
4.2.2 is nice, but nothing really new

AW: No stock rooted 4.2.2 rom?
Wow, I'm really unhappy to see this dumb answers here at xda.
I'm really ashamed of this behavior.
I think, we don't have a stock rooted odexed or deodexed rom here, because the Nexus 7 isn't the real developer device. On nexus 4 and Galaxy Nexus there are those roms.
I hope to have those rom here in a while.
Edit: seriously, guys, then giving bad ideas with stock 4.2.1 and updating this with ota.
Why nothing using the stock 4.2.2 directly? It is free to download.
Sorry, I'm really frustrated about those answers.

I don't use stock due to all the little hidden restrictions laying around it. I hate stock on any device :/
Sent from my MB612 using xda app-developers app
---------- Post added at 08:19 PM ---------- Previous post was at 07:53 PM ----------
Here it is.
http://forum.xda-developers.com/showthread.php?t=2148337
Sent from my Nexus 7 using xda app-developers app

AW: No stock rooted 4.2.2 rom?
As ive said
Great!
Send from my iPhone 6s

You can get the stock factory images directly from Google (search for "Factory Images for Nexus Devices" - xda won't let me post links), but they don't even have 4.2.1 anymore, just 4.2.2 . You *should* be able to install those directly.
I'm getting some odd "can't open /tmp/update.zip (bad)" messages on install though which I haven't gotten on prerooted roms.

Easy way to root the new stock 4.2.2 and install it full image.
To the OP there is a way to get the original full factory image for your nexus device. Here is the link.
https://developers.google.com/android/nexus/images
You can find the nakasi image 4.2.2 and download the tar image.
Then I would download and install the google nexus 7 toolkit here,
http://forum.xda-developers.com/showthread.php?t=1809195
Then install the sdk manager and update.
http://developer.android.com/tools/help/sdk-manager.html
Once all is installed then in the toolkit make sure you install the android usb drivers. I would then reboot your pc.
Then take the factory tar image and move it into a folder called "put factory image here" in the nexus 7 toolkit program files.
Then follow directions to flash it. You can then after it is flashed follow directions to root it.
Now you have a stock rooted version of 4.2.2. That is what I did and it worked for me. I am no expert by any means. I hope this helps.
I am not sure why I can't post links to help but if I have done something wrong please delete my links to the google factory image. If you google nexus 7 factory image you should find it.
R

These things take a little bit of time. 4.2.2 JUST rolled out, and the code was later dropped to AOSP. It will take a few days for the minds (who have other stuff to do, like jobs, families, etc.) to set everything up.
Also, Wugs root toolkit makes this process pretty idiot proof. I'm unsure if he has updated it to include 4.2.2, but you should definitely check it out.
---------- Post added at 04:17 PM ---------- Previous post was at 04:04 PM ----------
FormelLMS said:
Wow, I'm really unhappy to see this dumb answers here at xda.
I'm really ashamed of this behavior.
I think, we don't have a stock rooted odexed or deodexed rom here, because the Nexus 7 isn't the real developer device. On nexus 4 and Galaxy Nexus there are those roms.
I hope to have those rom here in a while.
Edit: seriously, guys, then giving bad ideas with stock 4.2.1 and updating this with ota.
Why nothing using the stock 4.2.2 directly? It is free to download.
Sorry, I'm really frustrated about those answers.
Click to expand...
Click to collapse
It has nothing to do with the 7 not being "the real developer device." Nothing is further from the truth. ROMs available for the Galaxy Nexus and Nexus 4 aren't here because the devs simply DONT HAVE A NEXUS 7. Why would a developer make a ROM for a device they don't own? It's the same reason there are ROMs for the Nexus 7 and not the others.
What I'm saying is you probably won't see those ROMs unless you take the time to port it yourself.
Developers on this site get really annoyed with those who have no idea how things work, and are also impatient for updates. This is a community, and we are given the opportunity to use free software these developers spend countless hours working on.
Learn to respect the developers and be as self reliant as you can. The tools are here at your disposal.

As the post above makes abundantly clear, 4.2.2 just rolled out yesterday and in roughly 24 hours Google posted the full factory images, and voila, now there's even a deodexed and and odexed and rooted too stock 4.2.2 ROM available - this stuff takes time, but it sure seems like some *cough*people*choke* are pretty damned impatient sometimes.
Kids... I tell ya.

omg why isn't cm11 out yet????

Yeah, where's those key lime pie custom roms ?
Sent from my Galaxy Nexus using xda app-developers app

I apologize of it seems that I don't know how to flash ota, I do. I am actually on 4.2.2 and was just asking a quedtion,. Sorry if you took out as me being stupid...
Sent from my Nexus 7 using Tapatalk 2

That's what I did last night, Factory image, rooted it, etc. Got the update notification, copied the update to my main sd card location and installed it through recovery. No issues, still getting some apps re-installed , etc.
mkoch820 said:
I restored 4.2.1 factory image, and got the message to upgrade in minutes. After that I managed to root with the usual method. Same adb commands, recovery and SU is working as in 4.2.1
4.2.2 is nice, but nothing really new
Click to expand...
Click to collapse

heccubusxda said:
Yeah, where's those key lime pie custom roms ?
Click to expand...
Click to collapse
Look in "Nexus 7>Nexus 7 KLP Development". There are plenty of them.:laugh:

Haha, good joke to let me explain, what developers do. Making fun here

Really New to Android.
br0adband said:
This, a thousandfold. If you can't do this yourself - meaning you choose to not learn how to do it yourself, more often than not, and expect people to hold your hand and just fulfill the GIMME GIMME GIMME nature - then why bother, stick with stock and be done with it.
Took me what, 5 minutes to do a clean install of 4.2.1, root it, install CWM, use CWM to install the 4.2.2 update, and remained rooted.
Is it really so tough to learn how to do some things yourself? I wonder...
Click to expand...
Click to collapse
Wow!!
I don't want to start off by being annoying but I was really saddened to read this. I'm new to Android. I got the N7 for Christmas. My first Android device. Love it!
I only had it a couple of days before I had it rooted (much easier than iPod). I wish I would have known not to update to 4.2.2 straight from the tablet. I had no idea it was going to unroot it doing it that way.
Any suggestions on weather I should do a clean install, re-root then use CWM (I'm guessing it stands for ClockWorkMod) to do the update or just wait to root the 4.2.2 .
Obviously I'm going to have to reinstall all my stuff if I do a clean install.
Any advice on the best way to do this would be great. I guess it shouldn't be that hard to learn how to do the updating using CWM
Thanks in advance.

termum55 said:
Wow!!
I don't want to start off by being annoying but I was really saddened to read this. I'm new to Android. I got the N7 for Christmas. My first Android device. Love it!
I only had it a couple of days before I had it rooted (much easier than iPod). I wish I would have known not to update to 4.2.2 straight from the tablet. I had no idea it was going to unroot it doing it that way.
Any suggestions on weather I should do a clean install, re-root then use CWM (I'm guessing it stands for ClockWorkMod) to do the update or just wait to root the 4.2.2 .
Obviously I'm going to have to reinstall all my stuff if I do a clean install.
Any advice on the best way to do this would be great. I guess it shouldn't be that hard to learn how to do the updating using CWM
Thanks in advance.
Click to expand...
Click to collapse
well buddy if i was you i would wait till wugs updates his tool kit it will be much easier but if your impatient like the rest of us just go in to wugs tool kit thread and download his kit it has an option to root since im assuming that youre unlocked all you have to do is re root it

What stuff can we can do with an unlocked bootloader?

Now that we have unlocked bootloader thanks to dan
What all things we can do?
1.have custom recovery?
2.flash different kernels.
This means we will soon have official CM versions and AOKP?
We will no more have to rely on current safestrap... and we can use CWM/Touch recovery and TWRP.
I m a newbie on this and will like you guyz to correct me or add more on this thing.
Thank you.

I think it's too soon to say we'll got a stable CM10 or aokp. But,we have entered a whole new life. This is just a beginning.
Nice to see some devs are still using this phone. Will see some custom roms soon. And we may see some custom kernels too. Rooting our phone is way easier than before. I can flash sbf without worrying to reroot using Ubuntu. Just flash cwm via fastboot and flash supersu. Damn! It just happens too fast. Lol.
Sent from my DROID RAZR using Tapatalk 2

Most important for me: you can downgrade to 4.0 and use lapdock properly!

So we can down grade
From my Atrix HD Maxx

[ROM][5.1] 9/17/2015-Lollipop Stock Rooted Google Play Edition LMY47O.H9

This is a Stock Google Play Edition Rom LMY47O.H9. It has no modifications besides being rooted
Devs feel free to use as a base, just give proper credit
Updated 9/17/2015
1. Make sure you do a wipe if coming from another rom
2. Flash in recovery
3. reboot(I suggest TWRP)
4. profit
It seems people on older firmware are having issues with wifi. This is due to your old firmware. If you are not S-off you will have to wait for your carrier to release updated firmware. There is nothing that can be done about it. :-/
If you have problems make sure you do a full wipe.. if you continue to have problems you need to be as detailed as possible.. What version firmware are you running? What ROM are you coming from? Are you bootloader unlocked? you need details.. if you don't give details you're more likely to get a better answer as to why it doesn't work from the fortune teller on the corner.
Also, please do not PM me for support. PM's will not be answered. Post it in the thread. It helps other's having the same issue find a solution. If it's over PM it only benefits you and not everyone else
H9 Update rom zip compiled by: @enewman17
Downloads:
5.1 LMY47O.H6: http://graffixnyc.com/m8.php#rom
DO NOT MIRROR
As this is a stock rom.. Nothing will be added.. No bug reports taken.. this is how it came right from Google with the exception of root
Disclaimer: I am not responsible if you use this and brick your device or if your device blows up, implodes, flames start shooting from it or it kills your neighbor's dog. Flash at your own risk. I am not responsible.... It was the other guy... I swear....
XDA:DevDB Information
Stock GPE Rooted, ROM for the HTC One (M8)
Contributors
graffixnyc, loserskater
ROM OS Version: 5.1.x Lollipop
Version Information
Status: Stable
Created 2015-04-08
Last Updated 2015-09-17

That was quick!!! Thanks Buddy!!

Keep this in mind, system write protection is enabled by default, the current module available does not yet work to disable write protection on GPe based roms.

Hi Graffixnyc, long time after s3. So I have att version and I am unlocking bootloader right now. i will install recovery after that and then, will this run on ATT version like a regular flash from recovery?

ceo.mtcl said:
Hi Graffixnyc, long time after s3. So I have att version and I am unlocking bootloader right now. i will install recovery after that and then, will this run on ATT version like a regular flash from recovery?
Click to expand...
Click to collapse
Hey dude!! I actually saw yourr other post in my thread but forgot to respond! How is everything?? It has been a while. Yes, it will run fine. I'm running it on my AT&T version.

seems super laggy to me, even the bootanimation. did a full wipe to.

I'm having issues as well with lots of lag and no camera or wifi.

odd, im flashed the backup version and its perfect

Will this work on the dev edition
Sent from my HTC One M8

Flashed this one and used the backup. The backup is more fluid than this for some reason.
Sent from my HTC One_M8 using Tapatalk

charlieb620 said:
Flashed this one and used the backup. The backup is more fluid than this for some reason.
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
I flashed this and I don't have any issues. I did a wipe before I did..

graffixnyc said:
I flashed this and I don't have any issues. I did a wipe before I did..
Click to expand...
Click to collapse
I'll try again.
Sent from my HTC One_M8 using Tapatalk

charlieb620 said:
I'll try again.
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
It didn't seem laggier to me.. But I have since restored my data.. Let me try with a fresh system wipe and play with it for a bit

Seems fine to me.. I wiped and flashed and it doesnt seem laggy to me so far.. I'll keep playing with it but it seems just as good as the cwm back up version for me

Trying to install via PhilZ CWM and getting this:
Creating links and setting perms...
set_metadata_recursive: some changes failed
Edit: redownloading, checking sums and such.

Yup did a full wipe. Laggy. Lock screen, waking, sleeping and drawer
Sent from my HTC One_M8 using Tapatalk

Fixed it. Had to specifically format /data for some reason. A full wipe wasn't cutting it.

Running smoothly here. Full wipe using Philz. Well chose the Install new rom option or whatever it's called. No lag!
Though question.. Since this is just the stock GPE ROM, does that include the stock recovery? Philz came up saying that the ROM may try to flash a recovery on boot and whether I want this to happen.. chose no.. but not sure what's going on.

BAM1789 said:
Running smoothly here. Full wipe using Philz. Well chose the Install new rom option or whatever it's called. No lag!
Though question.. Since this is just the stock GPE ROM, does that include the stock recovery? Philz came up saying that the ROM may try to flash a recovery on boot and whether I want this to happen.. chose no.. but not sure what's going on.
Click to expand...
Click to collapse
You were correct to chose no. It doesn't flash a recovery. Chainfire uses the install-recovery.sh script file for root purposes. twrp knows about this I believe since chainfire works directly with dees troy..

Build.prop changes?
I feel like my new M8 is almost perfect. Going from AT&T bloatware to a almost Nexus experience! Thank you so much for the hard work! One question and hopefully it isn't a noob question but I always change my LCD density down to 380 as I feel stock is huge! Do we need S-off to be able to change that in build.prop as I can edit it but it doesn't change anything. Thanks in advance for any info.

custom recovery on the active

Ok I have been reading a couple of forums and some people say you can out a custom recovery on the active and some say you would only brick your phone trying. I have it rooted, I would like to try a custom ROM but I am used to the galaxy s3 and the htc one m8 in the way of custom Roms which are easy to do.

brianisawesome1 said:
Ok I have been reading a couple of forums and some people say you can out a custom recovery on the active and some say you would only brick your phone trying. I have it rooted, I would like to try a custom ROM but I am used to the galaxy s3 and the htc one m8 in the way of custom Roms which are easy to do.
Click to expand...
Click to collapse
depending on which active you have if you have the international version with the unlocked bootloader your good with custom roms but if you have the at&t model I537 that had a locked bootloader you can not run custom roms on it.

brianisawesome1 said:
Ok I have been reading a couple of forums and some people say you can out a custom recovery on the active and some say you would only brick your phone trying. I have it rooted, I would like to try a custom ROM but I am used to the galaxy s3 and the htc one m8 in the way of custom Roms which are easy to do.
Click to expand...
Click to collapse
but if you have the at&t model I537 that had a locked bootloader you can not run custom roms on it.
Click to expand...
Click to collapse
I'd like to clarify a bit. Yes the AT&T model has a locked bootloader and yes this restricts what you can do on the phone, but that doesn't mean you can't have custom roms on this phone. You can't have a true custom recovery BUT there is something you can install called Safestrap that gives you virtually all the functionality of a custom recovery (plus it's based directly off TWRP so it looks and feels like a recovery). As far as roms, well, you can't install cyanogenmod or anything AOSP. Any rom you flash needs to have a stock kernel and be stock-based. There are very few roms written specifically for the i537, BUT you can install certain S4 roms using this patch to make them compatible.

thisisapoorusernamechoice said:
I'd like to clarify a bit. Yes the AT&T model has a locked bootloader and yes this restricts what you can do on the phone, but that doesn't mean you can't have custom roms on this phone. You can't have a true custom recovery BUT there is something you can install called Safestrap that gives you virtually all the functionality of a custom recovery (plus it's based directly off TWRP so it looks and feels like a recovery). As far as roms, well, you can't install cyanogenmod or anything AOSP. Any rom you flash needs to have a stock kernel and be stock-based. There are very few roms written specifically for the i537, BUT you can install certain S4 roms using this patch to make them compatible.
Click to expand...
Click to collapse
What are the risks of using said safestrap?
Sent from my SAMSUNG-SGH-I537 using XDA Free mobile app

brianisawesome1 said:
What are the risks of using said safestrap?
Sent from my SAMSUNG-SGH-I537 using XDA Free mobile app
Click to expand...
Click to collapse
Not much really. You can make nandroid backups so if you do mess up you can always restore. There haven't been any bugs with the last build and as long as you're using it to flash software meant for the i537 (or S4 roms with the masterpatch) it's perfectly safe. Honestly the only danger I can really envisage-and this would apply to any custom recovery-sometimes things take a long time to flash, you just have to make sure to have at least 70% battery when doing anything in recovery, having your battery die mid-flash would probably be bad. Sorry for my rambling answer, the main point is it is just as safe as a custom recovery on another device.

thisisapoorusernamechoice said:
Not much really. You can make nandroid backups so if you do mess up you can always restore. There haven't been any bugs with the last build and as long as you're using it to flash software meant for the i537 (or S4 roms with the masterpatch) it's perfectly safe. Honestly the only danger I can really envisage-and this would apply to any custom recovery-sometimes things take a long time to flash, you just have to make sure to have at least 70% battery when doing anything in recovery, having your battery die mid-flash would probably be bad. Sorry for my rambling answer, the main point is it is just as safe as a custom recovery on another device.
Click to expand...
Click to collapse
Ok so I have safestrap. What the updated list of Roms? What do I have to do after or before flashing a rom? I wanna make sure I don't brick my device lol and also why is my backup going to be 8gb????
Sent from my SAMSUNG-SGH-I537 using XDA Free mobile app