Some background info:
Nexus 5
Unlocked Bootloader
TWRP
Running Purity Rom
I have been running this Rom for about 2 months with no major issues. Now I am being prompted to do an OTA to 4.4.3. If I was stock that would be normal and expected but I am not sure what to do in my situation. I can not stop the prompt, I clear it from my notification window and it just appears back in 10 seconds or so.
I have tried to figure it out but cant find anything on the Purity thread, and I cant post my question there because I don't have 10 posts...
Any help would be greatly appreciated. I apologize if this answer is in a million places and I didn't see it.
Do not accept the OTA. Flash another rom if you want rid of the notification
Sent from my Nexus 5 using Tapatalk
rootSU said:
Do not accept the OTA. Flash another rom if you want rid of the notification
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
it would fail anyways wouldnt it? since im sure some stock files were modified/missing.
Zepius said:
it would fail anyways wouldnt it? since im sure some stock files were modified/missing.
Click to expand...
Click to collapse
Well yes, true but what's the Point trying ever?.better he knows
Sent from my Nexus 5 using Tapatalk
rootSU said:
Well yes, true but what's the Point trying ever?.better he knows
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Thanks for the help.
With that being said, Is it even possible to update the ROM I'm currently using without doing a wipe. They have released a few new versions since I flashed.
I use cataclysm and I don't want to switch roms. Does any one know how to remove the update notification? I've never had arom ask me to install it before
Sent from my Nexus 5 using Tapatalk
abrcrmdl23 said:
I use cataclysm and I don't want to switch roms. Does any one know how to remove the update notification? I've never had arom ask me to install it before
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I am in a pretty similar situation. At this point I'm happy with the stability and performance of the build I'm on. Upgrading to 4.3.3 isn't a huge concern at this moment. I just don't have the time to reconfigure all applications and settings if I have to do a wipe.
Figured out I out if you disable viewing notifications from the Google play services app the notification will go away.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Nexus 5 using Tapatalk
basik17 said:
Thanks for the help.
With that being said, Is it even possible to update the ROM I'm currently using without doing a wipe. They have released a few new versions since I flashed.
Click to expand...
Click to collapse
Reading Puritys thread, you can dirty flash it, but do it at your own risk. I read quite a bit of success doing it.
I run Purity 4.4.3 and it's really nice.
But like I said, either disable it if you don't care for the update, or try a dirty flash.
Or back everything up, and wipe, then flash and then restore.
But I take no responsibility for what may happen if you dirty flash, or anything.
Pr0meth3us said:
Reading Puritys thread, you can dirty flash it, but do it at your own risk. I read quite a bit of success doing it.
I run Purity 4.4.3 and it's really nice.
But like I said, either disable it if you don't care for the update, or try a dirty flash.
Or back everything up, and wipe, then flash and then restore.
But I take no responsibility for what may happen if you dirty flash, or anything.
Click to expand...
Click to collapse
I forgot to come back and update this thread. The issue for me was resolved by doing a dirty update, with no wipes at all. Obviously do a nandroid back up in your respective recovery first.
Thanks for the help folks
Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
THIS IS JUST A QUICK TOOL I MADE FOR NEXUS 7 NEW EDITION. IT UNLOCKS THE BOOTLOADER, FLASHES A CUSTOM RECOVERY AND GAINS ROOT.
This Voids Your Warranty And Im Not Help Responsible for Any Damage...(You Know The Rest)
INSTRUCTIONS
1. Install The Devices Drivers
2. Download The .zip
3. Extract And Open "Quick Root Tool"
4. Follow Prompts
Click to expand...
Click to collapse
DOWNLOAD
Quick Root Tool
Click to expand...
Click to collapse
CHANGELOG
Version 1.0(ALPHA) - Initial Release
There is no T-Mobile variant!
A 4gLTE variant will come out in the near future but now we are WIFI ONLY!
I belive you are looking for the OLD Nexus 7's forums :/
Thread moved - if this is still not the correct place, please let me know.
Kwongger said:
There is no T-Mobile variant!
A 4gLTE variant will come out in the near future but now we are WIFI ONLY!
I belive you are looking for the OLD Nexus 7's forums :/
Click to expand...
Click to collapse
Sorry, was writing the guide late last night and got confused, its for only the 2013 variant!
twrp is asking for a password and my tablet is stuck in boot loop
sneekerpimpz said:
twrp is asking for a password and my tablet is stuck in boot loop
Click to expand...
Click to collapse
Just hit cancel for Twrp password. Also this may have the same issue as the other root tool, if you aren't flashing a rom after unlock and root you must clear data in Twrp. There are threads around here about it, in general I believe. Try booting back into bootloader then Twrp and wipe data, see if it boots. I fixed mine this way. If not there is a restore dead nexus 1 click in the development forum that'll get you up and running again.
Sent from my SGH-I747 using Tapatalk 2
kept failing the wipe, i had to format then wipe and its up and running, thanks.
sneekerpimpz said:
kept failing the wipe, i had to format then wipe and its up and running, thanks.
Click to expand...
Click to collapse
Good to hear. I think more instructions should be in the op, like the data wipe If not flashing a custom rom.
Sent from my SGH-I747 using Tapatalk 2
no it saying I have to manually reroot because super user has no binaries so Im not rooted
Either try update the binaries or grab the su. Zip from the manual root thread and flash in twrp
Sent from my SGH-I747 using Tapatalk 2
sneekerpimpz said:
no it saying I have to manually reroot because super user has no binaries so Im not rooted
Click to expand...
Click to collapse
oh, sorry about that, this tool is an alpha(do not have the device but has been tested) as for the bootloop part the program asks you if your stuck in a bootloop then directs you to a thread that fixes that as these are 2 different processes.
this tool is classed as development, and the unbrick process is part of trouble shooting and help!
Tool Not Available
Hi,
Checked Mega and it says that the tool has been removed. Is there any other link to download this tool.
Thanks.
deveshprabhu said:
Hi,
Checked Mega and it says that the tool has been removed. Is there any other link to download this tool.
Thanks.
Click to expand...
Click to collapse
Use NRT toolkit by wugfresh... It's working for our N7 2013... everything just one click...
This thread has been created strictly for
Questions and Answers
[SIZE=+2]Dealing with[/SIZE]
OmniROM
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[SIZE=+2]This thread has been created for people to share issues and question they may encounter while using OmniROM
Dev Thread: Click Me![/SIZE]
[SIZE=+1]Please Do not clutter the Development thread with non related development chatter[/SIZE]
.
Please read the OP in dev thread carefully, it has some very important info in it.
Reserved
Nice I don't know if it's already fixed , or if it's an aosp browser bug/glitch but the transiction from browser to another app/home is a bit flickered , like seeing 3 times the browser page in that black screen transiction (when it must be all black) anyone can try that ?
Inviato dal mio Nexus 5 utilizzando Tapatalk
0 legacy obb
Ok, when I go to install the rom on cwm, when I install from sd card, it just shows the options
/0
/legacy
/obb
0 is my ds card, but don't I need to install the Ron on the root. If so then this is my root and I don't know how I can push a file to show with these three folders. Looking forward to trying the rom though
On the stock ROM, Spotify would resume playing once I enter my car and the phone establishes a bluetooth connection. This no longer happens on Omni. Anyone know how to get it back to stock behavior?
Also, is the default auto brightness settings the same as stock?
Lol nice thread but as your titles says it is q&a.
Does the ROM carry anything over that is specifically Google owned, such as the keyboard , camera, and especially the GEL launcher?
Sent from my Nexus 5
How long dos the rom take to boot the first time? Mine is taking ages
Can this ROM be used with Franco kernel?
Sent from my Nexus 5 using xda app-developers app
bgboii said:
Can this ROM be used with Franco kernel?
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
Yes.
I think most of the initial questions in this thread can be answered here: http://forum.xda-developers.com/omni/general
Is Multi Window enabled in the Nexus 5 builds? When will it be?
floepie said:
Does the ROM carry anything over that is specifically Google owned, such as the keyboard , camera, and especially the GEL launcher?
Sent from my Nexus 5
Click to expand...
Click to collapse
no. without flashing gapps, everything is AOSP.
Thanks a lot man!
Sent from my Nexus 5 using xda app-developers app
yumcax said:
Is Multi Window enabled in the Nexus 5 builds? When will it be?
Click to expand...
Click to collapse
Nope and when it's ready it'll be merged with the builds
I know there are a few unofficial builds already with it included, how unstable is MW atm? Anyone tested it on this device?
yumcax said:
I know there are a few unofficial builds already with it included, how unstable is MW atm? Anyone tested it on this device?
Click to expand...
Click to collapse
I guess it's unstable enough not to be included...
Do you think devs will not include it AS A it's correctly usable? Be patient.
Is this the correct gapps for the latest nightlie : pa_gapps-full-4.4-20131126-signed.zip?
Sent from my Nexus 5 using XDA Premium 4 mobile app
jrn2k said:
Is this the correct gapps for the latest nightlie : pa_gapps-full-4.4-20131126-signed.zip?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yes, you can use this one.
Google Hangout
Hi all,
After flashing this rom, my google hangout cannot login into my gmail account. It says that I do not have permission. I have tried 2 different google accounts and has the same issue.. I have wiped and re-flashed the rom and got the same issue. Is anyone else having the same issue? Or am I missing something?
henryjai said:
Hi all,
After flashing this rom, my google hangout cannot login into my gmail account. It says that I do not have permission. I have tried 2 different google accounts and has the same issue.. I have wiped and re-flashed the rom and got the same issue. Is anyone else having the same issue? Or am I missing something?
Click to expand...
Click to collapse
Which version of gapps did you flash?
Hey so i flashed costume rom the other day and then i wanted to return to stock so i flashed system.img and boot.img and now im 4.4 stock. I tried to flash 4.4.1/2 but i cant it says "faild" all the time from some reason.. any help ?
Please supply more details
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
rootSU said:
Please supply more details
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
Click to expand...
Click to collapse
Ok so two/three days ago i was on the stock rom ut then i wanted to change. I had an issue before with the updates so i kinda knew what to do all i did is to flash system.img and boot.img which i did. Then i rooted the device again and did all the process of returning my apps and all. I changed back to rom stock because all i wanted is to change kernel which i also did haha. So now im stock 4.4 with costume kernel. I thought it might be the costume kernel that mess it all up bu its not. When im trying to flash the 4.4.1/2 from the TWRP recovery it says failed.
If you installed a custom kernel you'll need to revert to the stock kernel to load the ota
sent from my hammerhead
ohad123454 said:
Ok so two/three days ago i was on the stock rom ut then i wanted to change. I had an issue before with the updates so i kinda knew what to do all i did is to flash system.img and boot.img which i did. Then i rooted the device again and did all the process of returning my apps and all. I changed back to rom stock because all i wanted is to change kernel which i also did haha. So now im stock 4.4 with costume kernel. I thought it might be the costume kernel that mess it all up bu its not. When im trying to flash the 4.4.1/2 from the TWRP recovery it says failed.
Click to expand...
Click to collapse
Dude, go back to the iPhone. You're all over the place in these threads. You need to read and learn a lot more before you do anything more on your phone. Not trying to be mean but you're going to end up messing up your phone beyond repair
jd1639 said:
Dude, go back to the iPhone. You're all over the place in these threads. You need to read and learn a lot more before you do anything more on your phone. Not trying to be mean but you're going to end up messing up your phone beyond repair
Click to expand...
Click to collapse
LOL. Nobody deserves an iPhone. Better to be the proud owner of a bricked N5. That said:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If you were previously on 4.4.1+ and flashed 4.4 it's failing is because the OTA package is looking for the 4.4 radio.
My advice would be to flash system and boot images for 4.4.2 since they are now available. No need to flash the OTA.
Sent from my Nexus 5 using Tapatalk
ldubs said:
If you installed a custom kernel you'll need to revert to the stock kernel to load the ota
sent from my hammerhead
Click to expand...
Click to collapse
I tried it but it didn't work. Ill try it again.
jd1639 said:
Dude, go back to the iPhone. You're all over the place in these threads. You need to read and learn a lot more before you do anything more on your phone. Not trying to be mean but you're going to end up messing up your phone beyond repair
Click to expand...
Click to collapse
i just wanna learn about android. i backup everything and don't worry about me i won't end up in a repair. I have probs and i thought that there are people in here that i could learn from and there are people like those. Otherwise thanks for your help in other threads. Have a nice day.
theesotericone said:
LOL. Nobody deserves an iPhone. Better to be the proud owner of a bricked N5. That said:
Click to expand...
Click to collapse
Haha ur right
El Daddy said:
If you were previously on 4.4.1+ and flashed 4.4 it's failing is because the OTA package is looking for the 4.4 radio.
My advice would be to flash system and boot images for 4.4.2 since they are now available. No need to flash the OTA.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Ok so all i need to do is just flash the system.img and boot.img of the 4.4.2 directly?
ohad123454 said:
Ok so all i need to do is just flash the system.img and boot.img of the 4.4.2 directly?
Click to expand...
Click to collapse
What about Radio?
rootSU said:
What about Radio?
Click to expand...
Click to collapse
And that haha
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
just saw this today not sure what caused it. I tried flashing one tweak to show battery % and noticed it then flashed back to stock. Even did a full wipe and restore with no fix.
Sent from my Nexus 5 using Tapatalk
remipmc said:
View attachment 2602769 just saw this today not sure what caused it. I tried flashing one tweak to show battery % and noticed it then flashed back to stock. Even did a full wipe and restore with no fix.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Looks like an Advertisement btw what tweak were u trying to make?
Just switching the battery icon to a percentage indicator. BTW that's supposed to be the player controls and they still work but the background seems to be messed up
Sent from my Nexus 5 using Tapatalk
remipmc said:
Just switching the battery icon to a percentage indicator. BTW that's supposed to be the player controls and they still work but the background seems to be messed up
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Ah ok, Is that now fixed? what music player is that?
Nope not fixed yet. Stock Google music player
Sent from my Nexus 5 using Tapatalk
remipmc said:
Nope not fixed yet. Stock Google music player
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Try clearing the app data and cache after force stopping it
No luck
Sent from my Nexus 5 using Tapatalk
wow..thats weird have you tried removing and performing a clean install of the app?
Can I remove Play Music?
Sent from my Nexus 5 using Tapatalk
remipmc said:
Can I remove Play Music?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Try uninstalling the update and then reinstall google play music and did u use any app to make that battery mod?
I had this issue running Droidkang ROM and for some time the cataclysm ROM, it is ROM specific and is not produced by stock. I posted about it but there was no solution from anyone other than redoing everything which I did, and it did not help.
varuntis1993 said:
Try uninstalling the update and then reinstall google play music and did u use any app to make that battery mod?
Click to expand...
Click to collapse
tried uninstall of the update - no effect
no app used, just flashed a zip file. already flashed back to stock - no effect
already wiped the cache - no effect
mistahseller said:
I had this issue running Droidkang ROM and for some time the cataclysm ROM, it is ROM specific and is not produced by stock. I posted about it but there was no solution from anyone other than redoing everything which I did, and it did not help.
Click to expand...
Click to collapse
i am not running a custom ROM. how can i verify that for everyone?
It is something to do with something that you have installed because mine did that until I got rid of my custom ROM/ kernel combination.
remipmc said:
tried uninstall of the update - no effect
no app used, just flashed a zip file. already flashed back to stock - no effect
already wiped the cache - no effect
Click to expand...
Click to collapse
I m now out of ideas...last thing I can tell you is to reboot ur phone in safe mode and also disable any xposed modules and then try.
Went ahead and did a factory restore and then re-rooted and all is good now
Sent from my Nexus 5 using Tapatalk
remipmc said:
Went ahead and did a factory restore and then re-rooted and all is good now
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I have been having the same problems. Stock rom, stock kernel. Tried factory restore and didn't fix it.
The rear-facing camera on my AT&T LG G3 D850 (now on Cricket) started acting up a few months ago. It would work for a few seconds, then purple lines would appear and would crash. I could get it to work sometimes for a few pics but then it would crash every time. I tried another camera app. I tried it in safe mode. I uninstalled the camera app and let it reinstall. I did a factory reset. I even ordered a new camera and installed it. None of these have fixed the issue. Now almost every time I open the camera app it just crashes and gives the message "Unfortunately, Camera has stopped." It works for a little bit maybe one out of 50 times I open it. The front-facing camera works fine. I posted on another site and a few people have said they have the same issue but no idea how to fix it. Please help.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Are you running factory stock non rooted Etc?
Sent from my iPhone using Tapatalk
hyelton said:
Are you running factory stock non rooted Etc?
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
Sorry, yes I am. It was rooted but stock OS, but unrooted before I did factory reset.
brian1269 said:
Sorry, yes I am. It was rooted but stock OS, but unrooted before I did factory reset.
Click to expand...
Click to collapse
If it was rooted doing a factory reset won't reset anything that may have changed during root. If flashing it back to stock doesn't fix it it would be a hardware issue.
Sent from my iPhone using Tapatalk
hyelton said:
If it was rooted doing a factory reset won't reset anything that may have changed during root. If flashing it back to stock doesn't fix it it would be a hardware issue.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
OK so I will look up how to flash the stock rom on it. I'm guessing Marshmallow is not available yet?
brian1269 said:
OK so I will look up how to flash the stock rom on it. I'm guessing Marshmallow is not available yet?
Click to expand...
Click to collapse
No, only kitkat and you'd have to have to use an AT&T sim to be able to ota update to it. As well as now flashing back to stock is risky it downgrading from MM.
Sent from my iPhone using Tapatalk
hyelton said:
No, only kitkat and you'd have to have to use an AT&T sim to be able to ota update to it. As well as now flashing back to stock is risky it downgrading from MM.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
What do you mean it is risky downgrading form MM?
brian1269 said:
What do you mean it is risky downgrading form MM?
Click to expand...
Click to collapse
As it says. Some have bricked when downgrading from MM. Most have not but some have bricked. So it can brick when downgrading from MM.
But unless you changed something system wise when your rooted it seems you may have a hardware problem somewhere. But if you ever tampered with anything then it could be from that.
Sent from my iPhone using Tapatalk
hyelton said:
As it says. Some have bricked when downgrading from MM. Most have not but some have bricked. So it can brick when downgrading from MM.
But unless you changed something system wise when your rooted it seems you may have a hardware problem somewhere. But if you ever tampered with anything then it could be from that.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
Never even opened up the phone before this. And I don't have MM, I have Lollipop. It won't let me upgrade to MM because I'm on Cricket.