Related
Hi guys, sorry for my english
I have a nexus rooted, stock room and cwm installed but i didint recive the ota update to 4.2.2
Its normal?
Enviado desde mi Nexus 7 usando Tapatalk 2
I concur, precisely the same situation, stock ROM, stock kernel but rooted
Have also tried to flash using the downloaded .zip but fails with an error code of 7.
Any ideas guys?
Sent from my Nexus 7 using XDA Premium HD app
AW: I cant recive ota update
It depends on which country you're in. I live in Germany and I still haven't got the update
Sent from my Nexus 7 using xda app-developers app
I live in chile, but the nexus was buy in EEUU
Enviado desde mi Nexus 7 usando Tapatalk 2
UK. Sat next to my sister who had received the update...
Could rooting be causing as problem because that's threw only difference between our devices, besides storage sizes, mine being a 16gb, hers being a 32gb.
I'm sure that won't matter, would it?
Sent from my Nexus 7 using XDA Premium HD app
Force stop and clear data in google play services a couple times. ( I think that's what it is) worked for me.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Numerous threads popping up all over asking the same questions, Mods are going to shut & lock many of these out soon - suggest that one read and use the SEARCH button. My OTA was downloaded already and ready to install but choose to wait 48 hours first.
4.2.2 rollout is for USA / North America now - gradually - and OTA if you are essentially running stock rom & kernel - simple update without losing Apps or data (CWM backup, always, as best practices) - took me 15 minutes from downloading, prep & backup to actual flashing and reboot, etc.
I opted to take a shortcut and went from 4.1.2 directly to 4.2.2 using the zipped, deodexed rooted version w busy box - bootloader stayed on 3.41 running JDQ39 now, smooth. I uninstalled the DSP/Beats Audio/Noozxoide EIZO-rewire audio Apps, just in case - and reinstalled EIZO from Play Store afterward, freeze Chrome browser & switched back on Boat Browser w. Flash Player, OTG mount is working for external USB, etc.
Using N7 from other regions of the world, download using the links here on XDA, check MD5's and then go thru the steps - profit & enjoy.
Just to confirm then, and this will help a lot of other users:
Being on a stock but rooted rom with a stock kernel would make no hindrance to receiving the ota update, and the advice for people experiencing this situation would be to just be patient and wait?
Sent from my Nexus 7 using XDA Premium HD app
licaxda said:
I concur, precisely the same situation, stock ROM, stock kernel but rooted
Have also tried to flash using the downloaded .zip but fails with an error code of 7.
Any ideas guys?
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
I had same problem, I downloaded stock image of 4.1.2, flashed and found my n7 going in to the bootloop. Downloaded stock image of 4.2.2, flashed and everything is ok. Restored with carbon backup. That is all.
Sent from my Nexus 7 using Tapatalk HD
licaxda said:
Just to confirm then, and this will help a lot of other users:
Being on a stock but rooted rom with a stock kernel would make no hindrance to receiving the ota update, and the advice for people experiencing this situation would be to just be patient and wait?
Click to expand...
Click to collapse
Yes, my N7 was on rooted 4.1.2 factory rom & stock kernel, with minor tweaks for audio, Chrome browser frozen but no major mods otherwise, and the OTA file was downloaded already on the device when I checked yesterday, ready to install. From various threads posted in the last 48 hours, it's a mixed bags - some install easily while others ran into problems, reasons varied & solutions simple to unknown. I opted for a safer approach - reverse some of my tweaks/uninstalled the audio tweaks, unfreeze Chrome, rebooted & then wipe, before using CWM to flash. It was easy, rebooted and up & running in less than 10 minutes, ALL of the apps & data intact and no FC'd.
For (folks in Europe or Asia, etc.) not willing to wait or access to OTA and prepared to do it on your own (thus, taking the risks, however - small, do your backup first and save your data/settings/etc. with CWM or TWRP and Titanium Backup - to a HDD or USB drive (suggested: 8GB & up) or PC - just in case, for restoration in the "unlikely event" that something go wrong.
Here's the XDA-linked Factory IMG 4.2.2 Nakasi file links, either odexed or deodexed (rooted, insecure boot, etc.) that I used - also, download the bootloader zip in post #2 (not required or needed, but in case you needed it or wanted to use it as the latest bootloader) - http://forum.xda-developers.com/showthread.php?t=2148337
Download, check MD5's and transfer to the N7. Next - launch into bootloader (make sure USB debugging is enabled & unknown source is allowed too) and WIPE dalvik cache and cache (2 times or 3 times each) - then selected the zip to flash. Once done, exit & reboot and wait for it to boot up for the 1st. time and allow it to settle for a few minutes. Click Settings & confirmed that I'm on 4.2.2 and check a few Apps for functionality. Let it sit & shutdown, reboot & proceed to restore most of my tweaks, played videos & music, surf the web to reconfirm that it's running smooth - next, do a new baseline CWM Backup.
Of course, YMMV - if it doesn't work for you, re-trace your steps and take your time, do not RUSH. If all else failed, go back to stock first 4.1 or 4.2 - then, update to 4.2.1 in its rooted state - your saved Apps & data, settings, etc. saved to your PC or USB/portable drive will eventually help you "rebuild" - just a matter of time. (If my other 2 HTC's are that easy to update from GB to JB, I would be very, very happy)
Please give credit for "thanks" to "teshxx" for preparing the Roms and refer to that thread for future questions ...
Good Luck to all.
Great information, thanks for the hefty reply, may be worth stickying for a few weeks I'm sure others will have the same questions.
I believe installing Beats audio can screw things up too? Can some one confirm?
Sent from my Nexus 7 using XDA Premium HD app
Hello all.
I have updated my samsung galaxy ace GT-S5830 to Android 4.4.2 KitKat with CyanogenMod 11 ROM.
I have had several problems but they all seem to have sorted themselfs out apart from a few glitches as follows
im using cooperfix v6.0.4.5 recovery and i have •Android 4.4.2 CyanogenMod 11 ROM for Galaxy Ace installed on card. I am unable to revert to CM7.2_JellyBreadv1_GT-S5830 using cooperfix v6.0.4.5 recovery as it aborts the instalation with a red triangle in the belly of the android bot and text.all the links i used to do it originly are dead links hotfile and another dead link. The only zip file it will install is the CM11 one.
Factory reset takes me back to cyanagemod boot screen and then the set up screen so its defaulting to CM11 and then in set up screen its imposible to set up gmail account and google play e.t.c. All the cooperfix files on here for older versions are dead links because of some federal law?
Wifi is perfect and connected straight away and the browser app works perfect connecting to the internet everytime.
so how can i get google play back again and working so i can install app and use it and if not possible to resync to google play how could i revert back to an older version. I really do prefer these custom roms but im struggling. Any help will always be appreciated and will always involve a thank you from me.
uksrevivor said:
Hello all.
I have updated my samsung galaxy ace GT-S5830 to Android 4.4.2 KitKat with CyanogenMod 11 ROM.
I have had several problems but they all seem to have sorted themselfs out apart from a few glitches as follows
im using cooperfix v6.0.4.5 recovery and i have •Android 4.4.2 CyanogenMod 11 ROM for Galaxy Ace installed on card. I am unable to revert to CM7.2_JellyBreadv1_GT-S5830 using cooperfix v6.0.4.5 recovery as it aborts the instalation with a red triangle in the belly of the android bot and text.all the links i used to do it originly are dead links hotfile and another dead link. The only zip file it will install is the CM11 one.
Factory reset takes me back to cyanagemod boot screen and then the set up screen so its defaulting to CM11 and then in set up screen its imposible to set up gmail account and google play e.t.c. All the cooperfix files on here for older versions are dead links because of some federal law?
Wifi is perfect and connected straight away and the browser app works perfect connecting to the internet everytime.
so how can i get google play back again and working so i can install app and use it and if not possible to resync to google play how could i revert back to an older version. I really do prefer these custom roms but im struggling. Any help will always be appreciated and will always involve a thank you from me.
Click to expand...
Click to collapse
install cwm5 to install roms prior to cm11.
-BRK- said:
install cwm5 to install roms prior to cm11.
Click to expand...
Click to collapse
Nice one thank you I have reverted back to gingerbread 2.3.6 via flashing cooper v1 and the md5 file in ODIN and its worked fine im running original stock rom with no problems. I have rerooted the phoneand installed CWM 5 recovery and looking into more stable custom roms as 11 is still in early stages.
Some of the problems i had were no camera/ no google play store / no connection / random bootloops/ alarm didnt switch off, and this really random one that the phone would ring but there was no way of answering it lol An exellent rom with brilliant potential and one i will use again but for now im experimenting with earlier versions that are more stable.
many thanks
The title says it all. Basically, I'm planning on doing an OTA upgrade from CM11 M10 to M11, and I want to know if there's any reason not to do this. I've done OTA for all the M builds since M8, but M11 is still so new that nobody has yet made a thread like this. Literally, googling "m11 ovation" yields nothing useful except the blog post and official download link.
Specifically, are there any driver/app issues, any glitches anywhere that don't appear in M10? Any apps that would interfere with the OTA? Any removed features not mentioned in the changelog or added ones that I might not want? Is there a corrupt package that will brick my tablet, as sometimes happens in the early days of a build rollout? Basically, anything, at all, anywhere that I should know (and the blog post won't tell me) before hitting the download button.
I've checked and even searching "m11 ovation" on CM Jira doesn't return anything newer than M8. My recovery version is the most recent required CWM upgrade for Cyanogenmod, I believe M8 or M9.
There should be no reason you should not be able to successfully update from M10 to M11 using the built in CM update feature. Just make sure that you have CWM version 6045 or newer installed to internal memory. If you don't, go to the dummies guide linked in my signature and install v6046 from post 7 there before attempting the update. And in case you want to revert to M10, boot to CWM and do a backup of M10 before updating.
Sent from my BN NookHD+ using XDA Premium HD app
leapinlar said:
There should be no reason you should not be able to successfully update from M10 to M11 using the built in CM update feature. Just make sure that you have CWM version 6045 or newer installed to internal memory. If you don't, go to the dummies guide linked in my signature and install v6046 from post 7 there before attempting the update. And in case you want to revert to M10, boot to CWM and do a backup of M10 before updating.
Sent from my BN NookHD+ using XDA Premium HD app
Click to expand...
Click to collapse
Thanks, I just rebooted into recovery and the version number says 6.0.4.6, so its all good. Update is in progress. So far its working, the little blue bar under the spinning Android thing is moving as expected, and the bootloader has successfully passed the baton to the OS, so no signs of a boot loop yet either.
Update is in progress. So far its working, the little blue bar under the spinning Android thing is moving as expected, and the bootloader has successfully passed the baton to the OS, so no signs of a boot loop yet either. The "Android is upgrading optimizing apps" screen has just popped up and is progressing nicely too. So far this is shaping up to be a replica of M10 but with most glitches gone and massively improved (we're talking sub-30secs whereas M10 would take easily 2-3 minutes).
So finally I got rid of my old HTC Bravo (which I'll keep as a treasure).
Now the problem that I have is that I got a Samsung Galaxy S3 Mini i8190L, which for what I have read is not rootable (please correct me if I'm wrong, I hope I am), so I start to check on different options for this matter and found a way to install an Android 4.1.2 Pre-Rooted ROM which allowed me to also install the TWRP 2.7 recovery. The once I had that installed I went over the CM 12.0 with the Gapps for it and got both flashed on my phone, I mean there is no complaint, it works amazingly great! and Lollipop is something completely awesome (even do looks like a Nexus), but My main problem is that I'd like to have root access and when I installed the Pre-rooted ROM had no problem, however when flashed the CM 12.0 realized that is not rooted and therefore SU does not work.
My question will be, is there any way to Root the S3 mini now that is on CM 12.0 (No Root), or is there any CM 12.0 ROM which comes Pre-rooted for S3 mini?
Soses said:
So finally I got rid of my old HTC Bravo (which I'll keep as a treasure).
Now the problem that I have is that I got a Samsung Galaxy S3 Mini i8190L, which for what I have read is not rootable (please correct me if I'm wrong, I hope I am), so I start to check on different options for this matter and found a way to install an Android 4.1.2 Pre-Rooted ROM which allowed me to also install the TWRP 2.7 recovery. The once I had that installed I went over the CM 12.0 with the Gapps for it and got both flashed on my phone, I mean there is no complaint, it works amazingly great! and Lollipop is something completely awesome (even do looks like a Nexus), but My main problem is that I'd like to have root access and when I installed the Pre-rooted ROM had no problem, however when flashed the CM 12.0 realized that is not rooted and therefore SU does not work.
My question will be, is there any way to Root the S3 mini now that is on CM 12.0 (No Root), or is there any CM 12.0 ROM which comes Pre-rooted for S3 mini?
Click to expand...
Click to collapse
Root is disabled by default in CM12. To enable root, go to settings > about phone and tap many times on build number (you will see a toast message that you are a developer now). Then go back and you will see the developers options
Hey thanks a lot indeed I was able to find that option after like hours of going around the phone what is really interesting is that I passed over the optionke thounsand times and never noticed! hahahahahaha But you're right from the setting os the ROM you can activate the root mode.
Hi all after trying hundreds of different roms on my old nexus. I think i have found the best way to boost the speed. I'm using xenonhd 5.1.1 with parrot mod and M-kernels. ??
Trying it out right now and it seems snappy. But I am using f2fs version of Xenonhd without the M kernel.
Give the xenonhd please...
Links please
GrandLuLu said:
Give the xenonhd please...
Click to expand...
Click to collapse
Sab3elbromba said:
Links please
Click to expand...
Click to collapse
A little "search" goes along ways......
https://forum.xda-developers.com/showthread.php?t=1826484
https://www.androidfilehost.com/?a=show&w=files&flid=23229
"Lightning fast" and "Nexus 7 2012" are not normally used in the same sentence.
Maybe I'll have to give this a try. I've kept mine on stock KitKat, and it's dog slow.
Are you using SuperSU as recommended by ParrotMod, or does it work with Magisk? Thanks.
Edit: To answer my own question, it seems to work fine with Magisk.
so, you have to downgrade the bootloader to use this?
beside that, in the xenonhd thread someone said .. after u install some apps you'll get the same slow down like on every other rom
https://forum.xda-developers.com/showpost.php?p=69949425&postcount=1817
I just got myself a new Nexus 7 and all i've done is run the updates up to 5.1 as 5.1.1 fails to install.
It is pretty slow and crashes a lot, I don't remember it being this laggy and slow when I first got one in 2012. Is it just a function of the new OS's or the new apps? What is the best build to be in for speed? I don't mind losing some of the newer features of the OS. Would just prefer something I can use without being frustrated...
Thanks
Sorry to ask this, but can the nexus 7 2012 roms be used on a nexus 7 3g 2012? are they the same? I am new to this model, I am about to buy one (just as ereader), but would like to have the best rom on it.
jbaumert said:
A little "search" goes along ways......
https://forum.xda-developers.com/showthread.php?t=1826484
https://www.androidfilehost.com/?a=show&w=files&flid=23229
Click to expand...
Click to collapse
The latest version update-XenonHD-09-13-15 is not available anymore. If anyone that has the files could share.
I was also pointed to try this rom: https://forum.xda-developers.com/nexus-7/development/rom-android-7-aosp-grouper-t3467514
And this one, but again no working links https://forum.xda-developers.com/showthread.php?t=2784244
I will buy today a Nexus 7 3G 2012 very cheap, so I will try some roms on it.
skinniezinho said:
Sorry to ask this, but can the nexus 7 2012 roms be used on a nexus 7 3g 2012? are they the same? I am new to this model, I am about to buy one (just as ereader), but would like to have the best rom on it.
Click to expand...
Click to collapse
To use a "Grouper" ROM on the "Tilapia / 3g" device, you just need to flash the Grouper ver of TWRP recovery. Granted, you will not have use of the 3g radio, but otherwise it will function normally.
jbaumert said:
To use a "Grouper" ROM on the "Tilapia / 3g" device, you just need to flash the Grouper ver of TWRP recovery. Granted, you will not have use of the 3g radio, but otherwise it will function normally.
Click to expand...
Click to collapse
Thanks. The device comes with 4.2.2 should I flash first 5.1.1 (in order to update radios and stuff) and then root=>recovery=>rom? Or should I just root it in 4.2.2?
If anyone have the older files that I pointed I would appreciate, I will test them and leave my feedback.
I would download the last "official" update from Google for your device (Tilapia I'm assuming), and manually flash the radio and bootloader with fastboot. (Granted, you could install the entire update, but why bother if you're going to put on a custom ROM anyways) Then, unlock the bootloader (if not already done) install TWRP recovery and flash away.
Anyone tested this ROM yet (with a bunch of apps installed to see if slows down or not) ?
jbaumert said:
A little "search" goes along ways......
https://forum.xda-developers.com/showthread.php?t=1826484
https://www.androidfilehost.com/?a=show&w=files&flid=23229
Click to expand...
Click to collapse
The download links are dead. :crying:
Jaguar10301 said:
I just got myself a new Nexus 7 and all i've done is run the updates up to 5.1 as 5.1.1 fails to install.
It is pretty slow and crashes a lot, I don't remember it being this laggy and slow when I first got one in 2012. Is it just a function of the new OS's or the new apps? What is the best build to be in for speed? I don't mind losing some of the newer features of the OS. Would just prefer something I can use without being frustrated...
Thanks
Click to expand...
Click to collapse
Root it and load RootBooster and choose the last option..
andynroid said:
Root it and load RootBooster and choose the last option..
Click to expand...
Click to collapse
I have a 2012 Nexus 7 running Resurrection Remix M (Android 6.0.1), and I can say that RootBooster *does* help. My N7 was *very* laggy and slow to respond when tapping on anything. I chose "Basic Mode -- Speed", re-booted and it's a LOT faster now. Time will tell if it lasts.
I've had MultiROM and TWRP on this tablet for quite awhile, so I also have RR-N installed as a secondary ROM. I'm going to try RootBooster on that ROM also.
I have a Nexus 7 2012 wifi model and need it strictly for Chromecast audio to control Pandora and Spotify.
What's the best rom for that?
Don't care for anything else really...
I installed the setup mentioned by the OP on my Nexus 7 2012, and it is working well so far. Thank you OP.
Initially I tried to use the kernel that is included with the XenonHD ROM, but it seemed to have issues with lag, not waking from sleep, etc. Then I switched to M Kernel and it was much better, so switching the kernel is necessary in my opinion.
Links:
Main XenonHD thread:
https://forum.xda-developers.com/showthread.php?t=1826484
XenonHD download:
The main download link in post #2 of the above thread doesn't seem to contain the download anymore. But if you go to the "Older builds" link, you can find the 08-20-15 build there. Here is a direct link.
https://androidfilehost.com/?fid=24052804347797659
M kernel:
I used the latest a77 version available from the main M Kernel thread here:
https://forum.xda-developers.com/showthread.php?p=38551156
ParrotMod:
I used the universal version available from the main ParrotMod thread here.
https://forum.xda-developers.com/ne...arrotmod-speed-2012-nexus-7-emmc-fix-t3300416
GApps:
I used the "nano" version from Open GApps:
http://opengapps.org/
Magisk:
Main thread and downloads here:
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
My Procedure:
I was starting with stock rooted Android 4.4.4. I had previously used the WugFresh toolkit to root and install twrp. If you have something older or custom, you may need to flash a recent stock rom first to update your bootloader.
1) Update to current version of twrp. I used the twrp app from the play store.
2) Boot into twrp. Factory reset.
3) Boot into Android.
4) Download XenonHD, M Kernel, ParrotMod, and GApps files to PC, transfer to tablet via USB. (or download on tablet)
5) Boot into twrp. Wipe everything except internal storage.
6) Install XenonHD, M Kernel, ParrotMod, GApps
7) Boot into Android. Be patient, first boot takes a while
I also replaced SuperSU with Magisk, because I don't consider recent non-Chainfire versions of SuperSU to be trustworthy. To do this:
1) Download Magisk and Magisk Manager to PC, transfer to tablet via USB. (or download on tablet)
2) Open SuperSU settings, select option to uninstall and prepare for alternate su manager.
3) Reboot to TWRP. Flash Magisk. Wipe cache/davlik (not sure this is necessary). Reboot to Android. IMPORTANT: If twrp says device does not appear to be rooted and prompts you to install SuperSU, you must decline.
4) In Android, install Magisk manager.
Hope this helps someone else.
spocko said:
I installed the setup mentioned by the OP on my Nexus 7 2012, and it is working well so far. Thank you OP.
Initially I tried to use the kernel that is included with the XenonHD ROM, but it seemed to have issues with lag, not waking from sleep, etc. Then I switched to M Kernel and it was much better, so switching the kernel is necessary in my opinion.
Links:
Main XenonHD thread:
https://forum.xda-developers.com/showthread.php?t=1826484
XenonHD download:
The main download link in post #2 of the above thread doesn't seem to contain the download anymore. But if you go to the "Older builds" link, you can find the 08-20-15 build there. Here is a direct link.
https://androidfilehost.com/?fid=24052804347797659
M kernel:
I used the latest a77 version available from the main M Kernel thread here:
https://forum.xda-developers.com/showthread.php?p=38551156
ParrotMod:
I used the universal version available from the main ParrotMod thread here.
https://forum.xda-developers.com/ne...arrotmod-speed-2012-nexus-7-emmc-fix-t3300416
GApps:
I used the "nano" version from Open GApps:
http://opengapps.org/
Magisk:
Main thread and downloads here:
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
My Procedure:
I was starting with stock rooted Android 4.4.4. I had previously used the WugFresh toolkit to root and install twrp. If you have something older or custom, you may need to flash a recent stock rom first to update your bootloader.
1) Update to current version of twrp. I used the twrp app from the play store.
2) Boot into twrp. Factory reset.
3) Boot into Android.
4) Download XenonHD, M Kernel, ParrotMod, and GApps files to PC, transfer to tablet via USB. (or download on tablet)
5) Boot into twrp. Wipe everything except internal storage.
6) Install XenonHD, M Kernel, ParrotMod, GApps
7) Boot into Android. Be patient, first boot takes a while
I also replaced SuperSU with Magisk, because I don't consider recent non-Chainfire versions of SuperSU to be trustworthy. To do this:
1) Download Magisk and Magisk Manager to PC, transfer to tablet via USB. (or download on tablet)
2) Open SuperSU settings, select option to uninstall and prepare for alternate su manager.
3) Reboot to TWRP. Flash Magisk. Wipe cache/davlik (not sure this is necessary). Reboot to Android. IMPORTANT: If twrp says device does not appear to be rooted and prompts you to install SuperSU, you must decline.
4) In Android, install Magisk manager.
Hope this helps someone else.
Click to expand...
Click to collapse
The Gapps don't seem to fit on the standard storrage anymore. Did you enlarge the system storage?
Nevermind, found what I didn wrong. Thanks for your post where you gather all the info
Strormrage said:
The Gapps don't seem to fit on the standard storrage anymore. Did you enlarge the system storage?
Nevermind, found what I didn wrong. Thanks for your post where you gather all the info
Click to expand...
Click to collapse
What was it in your case?