Related
Hi, have seen some posts for this issue but none really help me understand what went wrong (tried this update 3 times with same result)
I have nexus 5 with android 4.4.2, rooted with CF-Auto root.
Recently i received OTA update notification to 4.4.3, but when i'm trying to install it i get error without any info.
Before trying to update i completely uninstall xposed and all of its modules.
To my understanding using CF-Autoroot should not interfere with OTA updates.
Any ideas?
oshera said:
Hi, have seen some posts for this issue but none really help me understand what went wrong (tried this update 3 times with same result)
I have nexus 5 with android 4.4.2, rooted with CF-Auto root.
Recently i received OTA update notification to 4.4.3, but when i'm trying to install it i get error without any info.
Before trying to update i completely uninstall xposed and all of its modules.
To my understanding using CF-Autoroot should not interfere with OTA updates.
Any ideas?
Click to expand...
Click to collapse
did you do any other system modifications? change kernels?
I'd just dirty flash 4.4.3 and call it a day.
Zepius said:
did you do any other system modifications? change kernels?
Click to expand...
Click to collapse
Nop, unless apps like titanium backup or file manager (only other apps that require root) change something. :/
Lokke9191 said:
I'd just dirty flash 4.4.3 and call it a day.
Click to expand...
Click to collapse
Im no android expert(far from it), and prefer to stick to the most simple methods as long as i can run xposed framework.
this is why OTA without flashing or interfering with OS is best for me.
Keep this as last resort if no progress will happen regarding OTA updates.
Thanks!
oshera said:
Im no android expert(far from it), and prefer to stick to the most simple methods as long as i can run xposed framework.
this is why OTA without flashing or interfering with OS is best for me.
Keep this as last resort if no progress will happen regarding OTA updates.
Thanks!
Click to expand...
Click to collapse
OTA is more complex if you're rooted.. There's more flashing involved if you have / want a custom recovery (which all rooted users should aim to have)
Just download the full rooted stock ROM in android development and flash it without wipe from recovery.
It's actually fewer steps anyway.
OTA = revert system changes, boot recovery, flash, re-flash recovery, re-root
Rooted stock = boot recovery, flash
No brainer really. Flashing an OTA if rooted is a fool's errand
Sent from my Nexus 5 using Tapatalk
oshera said:
Im no android expert(far from it), and prefer to stick to the most simple methods as long as i can run xposed framework.
this is why OTA without flashing or interfering with OS is best for me.
Keep this as last resort if no progress will happen regarding OTA updates.
Thanks!
Click to expand...
Click to collapse
lmao, its FAR from the most simple method. most simple method would be to dirty flash a 443 stock/rooted rom and call it a day, without over complicating anything.
oshera said:
Hi, have seen some posts for this issue but none really help me understand what went wrong (tried this update 3 times with same result)
I have nexus 5 with android 4.4.2, rooted with CF-Auto root.
Recently i received OTA update notification to 4.4.3, but when i'm trying to install it i get error without any info.
Before trying to update i completely uninstall xposed and all of its modules.
To my understanding using CF-Autoroot should not interfere with OTA updates.
Any ideas?
Click to expand...
Click to collapse
Did you uninstall Xposed from within the app? If you simply uninstalled it the same way you install regular aps (by dragging to uninstall from the app drawer) then it doesn't completely uninstall.
marleyfan61 said:
Did you uninstall Xposed from within the app? If you simply uninstalled it the same way you install regular aps (by dragging to uninstall from the app drawer) then it doesn't completely uninstall.
Click to expand...
Click to collapse
Thank you!
That fixed my problem, after uninstall from within the app i could use OTA updates without flahing anything!
And thanks for everyone else for advises
oshera said:
Thank you!
That fixed my problem, after uninstall from within the app i could use OTA updates without flahing anything!
And thanks for everyone else for advises
Click to expand...
Click to collapse
Glad it worked for you. For future reference, do read this sticky - http://forum.xda-developers.com/google-nexus-5/general/info-nexus-5-ota-help-desk-t2523217
(along with the other stickies in that forum)
Hi Guys! Really hope you can help.
My Nexus 5 when I turned it on this morning booted up into 4.4.4 and suddenly showed that the process "com.android.systemui" has stopped. I rebooted several times and even cleared the cache through stock recovery and I still get the message. I have no idea what caused it. It was fine last night when I turned it off.
My phone is rooted and I do have a nandroid that is about two months old and I could boot TWRP using the Nexus Root Toolkit, but I was wondering if there is any other options? I would prefer not to lose anything up to this point.
I could kick myself for not making a more current nandroid. I've just been busy.
If the nandroid restore is the best approach could you refresh me on the exact options needed for both a clean restore with a nandroid and a dirty flash? I would probably dirty flash it first.
Hope you can help! Thanks so much!
Matthewlawson3 said:
Hi Guys! Really hope you can help.
My Nexus 5 when I turned it on this morning booted up into 4.4.4 and suddenly showed that the process "com.android.systemui" has stopped. I rebooted several times and even cleared the cache through stock recovery and I still get the message. I have no idea what caused it. It was fine last night when I turned it off.
My phone is rooted and I do have a nandroid that is about two months old and I could boot TWRP using the Nexus Root Toolkit, but I was wondering if there is any other options? I would prefer not to lose anything up to this point.
I could kick myself for not making a more current nandroid. I've just been busy.
If the nandroid restore is the best approach could you refresh me on the exact options needed for both a clean restore with a nandroid and a dirty flash? I would probably dirty flash it first.
Hope you can help! Thanks so much!
Click to expand...
Click to collapse
First of all, stop using the stock recovery.
Since you had root access, were you using any modifications such as Xposed?
You can pull your internal storage with adb pull /sdcard/, and your app data with adb pull /data/data/ while in custom recovery.
You can also try pushing a stock ROM .zip downloaded from here to your device with ADB push, then dirty flashing it in recovery (obviously after flashing a custom recovery, also assuming you're on stock ROM).
Also, don't use toolkits. Click the first link of my signature and read some threads if you don't know how to use ADB/fastboot.
On a sidenote I do have xposed framework installed. However, I've never had any problems out of it and I have not modified anything in months.
Matthewlawson3 said:
Hi Guys! Really hope you can help.
My Nexus 5 when I turned it on this morning booted up into 4.4.4 and suddenly showed that the process "com.android.systemui" has stopped. I rebooted several times and even cleared the cache through stock recovery and I still get the message. I have no idea what caused it. It was fine last night when I turned it off.
My phone is rooted and I do have a nandroid that is about two months old and I could boot TWRP using the Nexus Root Toolkit, but I was wondering if there is any other options? I would prefer not to lose anything up to this point.
I could kick myself for not making a more current nandroid. I've just been busy.
If the nandroid restore is the best approach could you refresh me on the exact options needed for both a clean restore with a nandroid and a dirty flash? I would probably dirty flash it first.
Hope you can help! Thanks so much!
Click to expand...
Click to collapse
Matthewlawson3 said:
On a sidenote I do have xposed framework installed. However, I've never had any problems out of it and I have not modified anything in months.
Click to expand...
Click to collapse
Read my previous post, and since you're running Xposed try using it's safemode disable feature, explanation on how that works here: http://forum.xda-developers.com/showpost.php?p=51306764&postcount=9879
Do you think this is caused by Xposed? You want me to disable it to see I assume?
Matthewlawson3 said:
Do you think this is caused by Xposed? You want me to disable it to see I assume?
Click to expand...
Click to collapse
It's entirely possible that a module/Xposed itself is causing a SystemUI crash, it's happened to me before. I'd do it just to be sure, then proceed to what I said in my previous post if it still happens.
Ok its been awhile since I dirty flashed. If I have to do that, what are the exact things that need to be cleared to maintain data after recovery?
Lethargy said:
It's entirely possible that a module/Xposed itself is causing a SystemUI crash, it's happened to me before. I'd do it just to be sure, then proceed to what I said in my previous post if it still happens.
Click to expand...
Click to collapse
Matthewlawson3 said:
Ok its been awhile since I dirty flashed. If I have to do that, what are the exact things that need to be cleared to maintain data after recovery?
Click to expand...
Click to collapse
What do you mean? No data is lost if you dirty flash a ROM, it only reformats /system.
Custom recovery, download stock ROM flashable zip, ADB push zip to your device while it's in recovery, then flash it.
It looks like I may not have to flash anything. The Xposed Disable worked. But how do I proceed if I want to use Xposed still?
Lethargy said:
What do you mean? No data is lost if you dirty flash a ROM, it only reformats /system.
Custom recovery, download stock ROM flashable zip, ADB push zip to your device while it's in recovery, then flash it.
Click to expand...
Click to collapse
Matthewlawson3 said:
It looks like I may not have to flash anything. The Xposed Disable worked. But how do I proceed if I want to use Xposed still?
Click to expand...
Click to collapse
First of all we have to see if it's an individual module or Xposed itself causing the issue. List your modules?
Disable all your modules, and delete /data/data/de.robv.android.xposed.installer/conf/disabled using a file explorer (to re-enable Xposed like the post says).
Reboot with no modules active, and see if it happens again.
If it doesn't, enable one module, reboot.
If it still doesn't happen, disable the module and enable a different one, reboot again. Keep doing it until you find the culprit.
OK.
My modules are AC Display, Bootmanager, DS Battery Saver, Google Search API, Gravity Box (KK), Greenify, Immerse Me, Notify Clean, Swype Tweaks, Xblast Tools, and Youtube Adaway.
Lethargy said:
First of all we have to see if it's an individual module or Xposed itself causing the issue. List your modules?
Disable all your modules, and delete /data/data/de.robv.android.xposed.installer/conf/disabled using a file explorer (to re-enable Xposed like the post says).
Reboot with no modules active, and see if it happens again.
If it doesn't, enable one module, reboot.
If it still doesn't happen, disable the module and enable a different one, reboot again. Keep doing it until you find the culprit.
Click to expand...
Click to collapse
Matthewlawson3 said:
OK.
My modules are AC Display, Bootmanager, DS Battery Saver, Google Search API, Gravity Box (KK), Greenify, Immerse Me, Notify Clean, Swype Tweaks, Xblast Tools, and Youtube Adaway.
Click to expand...
Click to collapse
Continue with what I've said to try, a few of your modules modify the system and could be causing it.
Go to the xposed module repository and find which of those modules updated recently. I'd bet that's the culprit. Or at least it's a good place to start looking.
Ok before I proceed. I have went into Xposed and disabled all modules. I am now in Root Explorer and have dug down to the "disabled" file following the path indicated. Do I just delete "disabled" and then reboot?
Lethargy said:
Continue with what I've said to try, a few of your modules modify the system and could be causing it.
Click to expand...
Click to collapse
Matthewlawson3 said:
Ok before I proceed. I have went into Xposed and disabled all modules. I am now in Root Explorer and have dug down to the "disabled" file following the path indicated. Do I just delete "disabled" and then reboot?
Click to expand...
Click to collapse
Yep, delete the folder named "disabled"
It may be faster to see which module updated recently and see if that fixes the problem first before going one by one. What do you think?
Lethargy said:
Yep, delete the folder named "disabled"
Click to expand...
Click to collapse
Matthewlawson3 said:
It may be faster to see which module updated recently and see if that fixes the problem first before going one by one. What do you think?
Click to expand...
Click to collapse
Worth a shot. In the end it's probably a single module, or a combination of conflicting modules, that's causing the issue.
Looks like the latest updated was Bootmanager on July 26.
Lethargy said:
First of all we have to see if it's an individual module or Xposed itself causing the issue. List your modules?
Disable all your modules, and delete /data/data/de.robv.android.xposed.installer/conf/disabled using a file explorer (to re-enable Xposed like the post says).
Reboot with no modules active, and see if it happens again.
If it doesn't, enable one module, reboot.
If it still doesn't happen, disable the module and enable a different one, reboot again. Keep doing it until you find the culprit.
Click to expand...
Click to collapse
Matthewlawson3 said:
Looks like the latest updated was Bootmanager on July 26.
Click to expand...
Click to collapse
Try enabling them one by one by update date.
I'll reboot with all modules off first. Ok, I no longer am getting the error message. At least it's not Xposed itself!
Matthewlawson3 said:
Looks like the latest updated was Bootmanager on July 26.
Click to expand...
Click to collapse
When I attempt to add a device to my LG G3 quick remote the list of manufacturers is empty, regardless of what type of device I select and in which room it is. What gives?
Remote
I'm currently having the same problem and I'm not sure how to fix it. Have you tried unrooting and going back to stock (if you have rooted, that is) and trying to use the phone as a remote as soon as you're done with setup? I haven't had a chance to, I think I might have accidentally uninstalled something I wasn't supposed to.
Have not tried and this is not important enough for me to mess with for the sake of trying.
GroovyGeek said:
Have not tried and this is not important enough for me to mess with for the sake of trying.
Click to expand...
Click to collapse
I know this is a little old, but I was having the same issue and found a solution. Freezing Quickset SDK in titanium backup caused it for me. Unfreezing it fixed it.
Are you doing this on a lollipop or a KitKat ROM, or the stock rom
I was experiencing this problem on Cyanogenmod 12, but managed to fix it based partially on information from this post.
Steps I took:
Removed previous version of Quick Remote with Titanium Backup.
Set SELinux to Permissive using SELinux Mode Changer.
Rebooted into recovery and install Quick Remote from the post linked above.
It seems that setting SELinux to permissive was the step I had been missing. Of course, permissive mode is less secure, but I'm glad to have my remote working again.
crescentmage said:
I was experiencing this problem on Cyanogenmod 12, but managed to fix it based partially on information from this post.
Steps I took:
Removed previous version of Quick Remote with Titanium Backup.
Set SELinux to Permissive using SELinux Mode Changer.
Rebooted into recovery and install Quick Remote from the post linked above.
It seems that setting SELinux to permissive was the step I had been missing. Of course, permissive mode is less secure, but I'm glad to have my remote working again.
Click to expand...
Click to collapse
HI,
I've recently changed my ROM to CM12 on my g3 and have been trying everything to get the manufacturer list to work and im having 0% luck. how would i go about changing my SELinux to passive as thats the only thing i haven't tried (Im new to rooting and installing custom ROM's )
also i was wondering if there is any chance you knew how to get the LG stock camera app to work without crashing upon launch?
Thanks
-Joe Barber
bpyazel said:
I know this is a little old, but I was having the same issue and found a solution. Freezing Quickset SDK in titanium backup caused it for me. Unfreezing it fixed it.
Click to expand...
Click to collapse
this one works 4 me, thanks m8
I just installed Lineage OS on my Nexus 5 and i checked via root checker my phone is not rooted. But still whenever i try to login in Snapchat it doesn't let me in. I tried many solutions like removing root access from SuperSu(when it was rooted) but still it doesn't help. So can anyone help with that?
vsaery said:
I just installed Lineage OS on my Nexus 5 and i checked via root checker my phone is not rooted. But still whenever i try to login in Snapchat it doesn't let me in. I tried many solutions like removing root access from SuperSu(when it was rooted) but still it doesn't help. So can anyone help with that?
Click to expand...
Click to collapse
Same issue with the note 4
It is an issue of kernel not passing "SafetyNet", which required to complete the login of Snapchat and some other applications.
Easy fix that worked for me on other ROM with same issue is,
1.) Download latest Franco Kernel (Franco Kernel currently passes SafertyNet, that's why).
2.) Backup your "Boot" partition in TWRP.
3.) Flash Franco Kernel. Then reboot.
4.) Login in your Snapchat, it should work this time around.
5.) Go back to TWRP, and use restore function to restore the previous "Boot" partition to get LineageOS kernel back.
Let me know how it goes.
parth7667 said:
It is an issue of kernel not passing "SafetyNet", which required to complete the login of Snapchat and some other applications.
Easy fix that worked for me on other ROM with same issue is,
1.) Download latest Franco Kernel (Franco Kernel currently passes SafertyNet, that's why).
2.) Backup your "Boot" partition in TWRP.
3.) Flash Franco Kernel. Then reboot.
4.) Login in your Snapchat, it should work this time around.
5.) Go back to TWRP, and use restore function to restore the previous "Boot" partition to get LineageOS kernel back.
Let me know how it goes.
Click to expand...
Click to collapse
this didn't work.. i tried installing franco kernel but still not logging in Snapchat
vsaery said:
this didn't work.. i tried installing franco kernel but still not logging in Snapchat
Click to expand...
Click to collapse
it worked.. thanks alot man.. i had to unroot again and then flash franco kernel to make it work
parth7667 said:
It is an issue of kernel not passing "SafetyNet", which required to complete the login of Snapchat and some other applications.
Easy fix that worked for me on other ROM with same issue is,
1.) Download latest Franco Kernel (Franco Kernel currently passes SafertyNet, that's why).
2.) Backup your "Boot" partition in TWRP.
3.) Flash Franco Kernel. Then reboot.
4.) Login in your Snapchat, it should work this time around.
5.) Go back to TWRP, and use restore function to restore the previous "Boot" partition to get LineageOS kernel back.
Let me know how it goes.
Click to expand...
Click to collapse
this works.. thanks
vsaery said:
this works.. thanks
Click to expand...
Click to collapse
No problem. Glad to be of service.
vsaery said:
I just installed Lineage OS on my Nexus 5 and i checked via root checker my phone is not rooted. But still whenever i try to login in Snapchat it doesn't let me in. I tried many solutions like removing root access from SuperSu(when it was rooted) but still it doesn't help. So can anyone help with that?
Click to expand...
Click to collapse
Do you have Xposed installed?
If yes, this is the issue. I have read, that the only soluton is to unistall Xposed, then install Snapchat, then login normally, then download Titanium Backup and backup the app, then reinstall xposed and use the backup to get yourself logged in.
Because this was too bothersome for me, I just installed CASPER, which is an alternative client for Snapchat, just make sure not to save too many snaps, you could get banned for that (I also read somewhere), in fact disable auto downloading snaps in the settings.
Nottrueuser said:
Do you have Xposed installed?
If yes, this is the issue. I have read, that the only soluton is to unistall Xposed, then install Snapchat, then login normally, then download Titanium Backup and backup the app, then reinstall xposed and use the backup to get yourself logged in.
Because this was too bothersome for me, I just installed CASPER, which is an alternative client for Snapchat, just make sure not to save too many snaps, you could get banned for that (I also read somewhere), in fact disable auto downloading snaps in the settings.
Click to expand...
Click to collapse
thanks for answering but i already found a solution.. you can check in other comment.
Franco kernel worked for me on my Nexus 5.
If you get logged out of Snapchat, the process must be repeated.
Curiously, my Nexus 7 can log on to Snapchat with the lineage kernel from lineage-14.1-20170228-nightly-flo-signed.zip ROM, no Franco kernel required.
First off, props to all developers working on the device. Fantastic developments in this subforum!
Secondly, would it be possible to spoof the device info on any rom to mimick the stock factory image? Reason I ask is I have an app, a type of banking app used locally, that does not seem to be working on this rom or any other.
It does work on stock rom. While currently i dont have root, i have tried magisk (with magisk app hidden) and magiskhide props, universal safetynet fix wth zygisk and lsposed etc.. nothing seems to work. I dont think it detects root as currently i am not even rooted on evolution rom. However, I think it detects a custom rom. Therefore, if it is possible to spoof either the rom or the app to show it that the phone is running the stock rom it might work.
If anyone knows a way to do this or some other way to try to access the app while being on a custom rom, please let me know.
Thanks.
Just a thought, detecting a custom ROM would mean the app would recognize ALL official ROMs? Kinda hard, so probably something else... When rooted, did you try whitelist instead of hide?
Thanks for the response.
I didn't whitelist at the time, I just added the app to the "denylist" of zygisk. That said, as mentioned above, I am not rooted and did a fresh install of Evolution ROM. App doesn't work.
I have previously done a clean install of the stock ROM and the app works perfectly there.
Hmm so it's not detecting the unlocked bootloader... That's really weird. Sorry I can't help
if you aren't rooted, magisk isn't going to work. the magisk forum is likely a better place to look for an answer
So I figured out why my banking app wasn't letting me use my fingerprint. You apparently have to turn off developer options to get the app to work properly.
Ah was thinking about that yesterday! Actually there's a Magisk module that could help, IAmNotADev I think it's called, it hides dev status from selected apps.
erispimp said:
So I figured out why my banking app wasn't letting me use my fingerprint. You apparently have to turn off developer options to get the app to work properly.
Click to expand...
Click to collapse
krakout said:
Ah was thinking about that yesterday! Actually there's a Magisk module that could help, IAmNotADev I think it's called, it hides dev status from selected apps.
Click to expand...
Click to collapse
Also after I registered my fingerprint with the app. I turned developer options back on and it was fine.
Haha so it only checks only until activated? Stupid...
krakout said:
Haha so it only checks only until activated? Stupid...
Click to expand...
Click to collapse
I'm guessing so.