Hi all, I am certain others are having this problem, but I couldn't find any threads about it.
Does anyone know how to get a reboot widget to work? I used to keep Quick Reboot on my home screen just to have easy access to recovery and other stuff. Since the Lollipop update, none of the reboot managers on the play store work.
Anyone know of a work around or alternative?
Is your phone rooted, from what i understand the app you're referring to or any like it requires it. If you are rooted most any custom rom will have the boot menu your looking for just not as a widget.
Holo Reboot works for me on OB7.
https://play.google.com/store/apps/details?id=com.scartech.holoreboot
It has a dark and bright widget.
Sent from my SM-N910P using Tapatalk
samep said:
Holo Reboot works for me on OB7.
https://play.google.com/store/apps/details?id=com.scartech.holoreboot
It has a dark and bright widget.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Dang, it doesn't work for me. It asks for root privileges and I grant them, then says your phone will reboot....but never does. It behaves the same way all reboot managers do, just bombs out.
It has been like this on every ROM I've used (Noterized, Alliance), including stock. WTF?? Are you certain it is rebooting your Note when you ask it to?
Even apps Like Synapse that came with my ROM cannot reboot. The Xposed module reboot function fails too. Like I said, it isn't specific to this ROM, it has always been like this for me on the NOTE 4.
pinetreehater said:
Dang, it doesn't work for me. It asks for root privileges and I grant them, then says your phone will reboot....but never does. It behaves the same way all reboot managers do, just bombs out.
It has been like this on every ROM I've used (Noterized, Alliance), including stock. WTF?? Are you certain it is rebooting your Note when you ask it to?
Even apps Like Synapse that came with my ROM cannot reboot. The Xposed module reboot function fails too. Like I said, it isn't specific to this ROM, it has always been like this for me on the NOTE 4.
Click to expand...
Click to collapse
I was using it with rooted OB7 stock using beta 2.49 SuperSU apk. Just flashed a custom ROM that uses 2.46 and does just as you say.
Try the beta 2.49. It was made for the lollipop kernel enforcing vs permissive mode issue.
http://forum.xda-developers.com/showpost.php?p=55256620&postcount=1 Shouldn't be beta, IMO.
Edit: that didn't fix it on custom ROM for me either. I'll look deeper into this.
Sent from my SM-N910P using Tapatalk
samep said:
I was using it with rooted OB7 stock using beta 2.49 SuperSU apk. Just flashed a custom ROM that uses 2.46 and does just as you say.
Try the beta 2.49. It was made for the lollipop kernel enforcing vs permissive mode issue.
http://forum.xda-developers.com/showpost.php?p=55256620&postcount=1 Shouldn't be beta, IMO.
Edit: that didn't fix it on custom ROM for me either. I'll look deeper into this.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
I have found that applications that issue a reboot command(like xposed), also fail to result in a reboot. However, interestingly enough, I just noticed that the reboot command from within Titanium works (it is inside the menu list).
Sometimes I notice when I try to reboot with a app, a toast message comes on a says "Reboot:Null" or "that function doesn't exist (or something like that)" as if that command functionality doesn't exist on the Note 4. I know it isn't a Lollipop issue, because my wife's G2 has Lollipop and Quickboot works flawlessly.
When Titanium successfully rebooted, it flashed a toast message (the first time). I didn't have a chance to read it all, it was long. But it seems to be using another method to initiate a reboot. Dunno, I am stumped.
pinetreehater said:
I have found that applications that issue a reboot command(like xposed), also fail to result in a reboot. However, interestingly enough, I just noticed that the reboot command from within Titanium works (it is inside the menu list).
Sometimes I notice when I try to reboot with a app, a toast message comes on a says "Reboot:Null" or "that function doesn't exist (or something like that)" as if that command functionality doesn't exist on the Note 4. I know it isn't a Lollipop issue, because my wife's G2 has Lollipop and Quickboot works flawlessly.
When Titanium successfully rebooted, it flashed a toast message (the first time). I didn't have a chance to read it all, it was long. But it seems to be using another method to initiate a reboot. Dunno, I am stumped.
Click to expand...
Click to collapse
I got some ideas just slow going setting up a fresh ROM. For stock, I had a highly customized setup, look and feel but everyone's preferences are not alike so I can't complain. Even with Titanium and TWRP tar to pull from, I had system customized too. I've got apps and lib folder to edit; some to copy over and some to delete. Keyboards have got to go; back to custom Swype with top number row and directional left right arrows. There's always the nandroid to restore but I'll try to set this up for a backup.
I'll chime in if I figure it out. Maybe just a matter of time. Not out of ideas yet. If someone has a solution, chime in.
Sent from my SM-N910P using Tapatalk
Related
Hi,
Since i can't post in the thread, so I just highlight in here.
I've been using this rom for about a month. This rom is really nice but since the new update, it gets even better. Only one small thing, the LED flashlight widget in the quickpanel didn't show up although you have tick it in the settings.
That's all. I hope someone could tell this to Spizzy01 so that he can fix this.
Thanks...
matfai said:
Hi,
Since i can't post in the thread, so I just highlight in here.
I've been using this rom for about a month. This rom is really nice but since the new update, it gets even better. Only one small thing, the LED flashlight widget in the quickpanel didn't show up although you have tick it in the settings.
That's all. I hope someone could tell this to Spizzy01 so that he can fix this.
Thanks...
Click to expand...
Click to collapse
Most probably Spizzy01 has removed the flashlight because there is a bug with camera !!
Really?? Well, I didn't know that....
Thanks for a fast reply...
Swipe to move switch icons? No, havent listened...
Aurora Play Problems
Hello,
I just installed Aurora Play 1.1.0 and I am having problems which I think might be related to superuser.
The Rom works fine, but anything that requires root access gets frozen in place. My phone is rooted, I am pretty sure of it - not only the bootloader is unlocked but also, I did manage to initially change the clock speed to 1.4 ghz, and that change has remained so far.
However, if, for example, I try enabling root access on the ES File Explorer, it simply freezes the app (sort of like it is waiting for the confirmation from Superuser, but it never comes). I only ever saw the superuser authorization screen once when I changed the clock at first.
I am pretty sure the OC is not the problem, since I reinstalled the rom and did no OC on the 1st time at all, but the same problem persisted.
I would try uninstalling SU and installing that other superuser app on the market to see if that would solve the problem, but I couldn't manage to uninstall it.
Any thoughts on this? I would love to solve this problem since this room is outstanding on all other accounts.
PS.: I followed all instructions to the letter, and like I said I tried reinstalling the rom already. I am using Lupus v10 (tried Lupus v11 before on the 1st installation).
Fenrir007 said:
Hello,
I just installed Aurora Play 1.1.0 and I am having problems which I think might be related to superuser.
The Rom works fine, but anything that requires root access gets frozen in place. My phone is rooted, I am pretty sure of it - not only the bootloader is unlocked but also, I did manage to initially change the clock speed to 1.4 ghz, and that change has remained so far.
However, if, for example, I try enabling root access on the ES File Explorer, it simply freezes the app (sort of like it is waiting for the confirmation from Superuser, but it never comes). I only ever saw the superuser authorization screen once when I changed the clock at first.
I am pretty sure the OC is not the problem, since I reinstalled the rom and did no OC on the 1st time at all, but the same problem persisted.
I would try uninstalling SU and installing that other superuser app on the market to see if that would solve the problem, but I couldn't manage to uninstall it.
Any thoughts on this? I would love to solve this problem since this room is outstanding on all other accounts.
PS.: I followed all instructions to the letter, and like I said I tried reinstalling the rom already. I am using Lupus v10 (tried Lupus v11 before on the 1st installation).
Click to expand...
Click to collapse
Please try downloading the following ZIP and flashing it VIA clockwork mod.
Let me know the results.
http://forum.xda-developers.com/attachment.php?attachmentid=1890140&d=1366191665
Spizzy01 said:
Please try downloading the following ZIP and flashing it VIA clockwork mod.
Let me know the results.
http://forum.xda-developers.com/attachment.php?attachmentid=1890140&d=1366191665
Click to expand...
Click to collapse
Can CWM coexist with TWRP? I think I only have TWRP installed. Or can I just use TWRP instead?
missing pixels in landscape app drawer
Spizzy, first and foremost congratulations on this great rom, it is fantastic! The only gripe I'm having is that when the app drawer is in Landscape mode it is cutting some pixels on the bottom (can't see the lower end of the blue highlight when using the ps controls). Other than that, all is perfect so far.
It worked!
Thanks a lot, Spizzy! Whatever that package was, it worked great and now superuser is not giving me any headaches anymore. Everything works great and the rom is blazing fast!
Just one thing - when I checked the info that comes up on the pachage before installing it, it said it was for locked bootloaders, but I assume that was a typo (since the zip file is for unlocked, and mine is unlocked as well). Just mentioning since it could maybe cause a little confusion on people downloading it in the future.
Oh and I did use TWRP in the end - I guess it's the same thing.
Figured I would start here in my device thread before trying the SuperSU thread.
Anybody have issues with SuperSU since the last few updates ago?
SuperSU does not even open. Root-dependent apps do not open. Titanium sits there at the initial screen "asking for root rights" until I kill the app. AdAway does not open... just goes right to a black screen until I kill the app. AdAway seems to work though, as my web surfing does not have ads.
I've also tried manually going in and applying the latest update via (philz) recovery.
Would I be safe to roll back to an older version of SuperSU?
Mods... if you're going to gun the thread, please at least point me in the right direction as I did search, but did not find anything related to recent issues on the Note 2 for SuperSU.
TIA for help and suggestions.
Oh yeah its still sitting in the play store. I lost root the last couple updates ago. I had to re flash my rom and start over.
ceabbott2 said:
Oh yeah its still sitting in the play store. I lost root the last couple updates ago. I had to re flash my rom and start over.
Click to expand...
Click to collapse
As part of my search, I did see Chainfire mention in his "fix" thread that some apps like wanam can cause issues. Of course, I have xsposed installed, so that could be the issue.
Do you (or did you) also have xsposed installed as well?
I have tried older versions of SU, uninstalling via philz then redownloading from Play - which now tells me the binaries are out of date and can't be done by SU, and I need to re-root.
Think I might try one of the other SuperUser apps "just to see how it works", or if it does.
lennykravitz2004 said:
As part of my search, I did see Chainfire mention in his "fix" thread that some apps like wanam can cause issues. Of course, I have xsposed installed, so that could be the issue.
Do you (or did you) also have xsposed installed as well?
I have tried older versions of SU, uninstalling via philz then redownloading from Play - which now tells me the binaries are out of date and can't be done by SU, and I need to re-root.
Think I might try one of the other SuperUser apps "just to see how it works", or if it does.
Click to expand...
Click to collapse
For me, I just reflashed the ROM I was running at the time and that resolved it. Of course seeing that the update was " fixed" I attempted it and lost root again. I then did the same as before, wiped and relashed. I didn't do clean installs either time. Just wiped caches and reflashed. That sucks if you have to re-root. I mean, it's easy and all but it shouldn't have to be done.
D
Before attempting any drastic measures (i.e., full wipe and reinstallation of the ROM), try this. This trick usually works for me.
Open your Application Manager, and locate your SuperSU application. Turn it off (i.e., click the "Turn Off" button). It may prompt you that updates are about to be uninstalled; that's ok. Download "BETA-SuperSU-v2.25.zip" and verify the MD5. Reboot into recovery and flash this file. Reboot and re-enable the SuperSU application from the Application Manager (it will be easy to find this time - scroll all the way over to the right, under "Turned Off"). Open SuperSU and it should let you reinstall the binaries.
Recently I've inexplicably lost root a number of times, and the above method has fixed it for me every time.
DJ_Barcode said:
Before attempting any drastic measures (i.e., full wipe and reinstallation of the ROM), try this. This trick usually works for me.
Open your Application Manager, and locate your SuperSU application. Turn it off (i.e., click the "Turn Off" button). It may prompt you that updates are about to be uninstalled; that's ok. Download "BETA-SuperSU-v2.25.zip" and verify the MD5. Reboot into recovery and flash this file. Reboot and re-enable the SuperSU application from the Application Manager (it will be easy to find this time - scroll all the way over to the right, under "Turned Off"). Open SuperSU and it should let you reinstall the binaries.
Recently I've inexplicably lost root a number of times, and the above method has fixed it for me every time.
Click to expand...
Click to collapse
Thanks for the try. Did not work though.
Looks like I just need to re-flash the ROM.
My problem was odd. Before I discovered the aforementioned trick, I'd re-root with Chainfire or Kingo. I'd reboot, and my device would be rooted. But those two methods have an additional payload - they flash the stock recovery. So I'd ODIN the Philz Touch recovery back to the device, reboot, and root would be gone. Never figured out what was going on.
Yup. Issues with new version. Only last 2 or three updates.
They seemed to be perfectly fine with cm12 though.
Sent from my SPH-L900 using XDA Free mobile app
Thanks for all of the input.
After doing a full wipe, and then re-loading Classic Stock 4.4.2, life is good again! Back to running awesome for a few weeks now.
Having said that, I did want to follow-up and ask others what current version of SuperSU you are on. As of right now, I am still on v2.01 (which is what was packaged with the ROM) and have not updated yet. Only other versions of SuperSU I have zips downloaded for are: 2.25 from post above, 2.36, and 2.37.
Any suggestions or confirmations on which newer/more recent versions will not bork my root status? Or which versions to definitely stay away from trying to use?
Thanks, and I appreciate any help and suggestions!
lennykravitz2004 said:
Thanks for all of the input.
After doing a full wipe, and then re-loading Classic Stock 4.4.2, life is good again! Back to running awesome for a few weeks now.
Having said that, I did want to follow-up and ask others what current version of SuperSU you are on. As of right now, I am still on v2.01 (which is what was packaged with the ROM) and have not updated yet. Only other versions of SuperSU I have zips downloaded for are: 2.25 from post above, 2.36, and 2.37.
Any suggestions or confirmations on which newer/more recent versions will not bork my root status? Or which versions to definitely stay away from trying to use?
Thanks, and I appreciate any help and suggestions!
Click to expand...
Click to collapse
The actual issue is not superuser or the updates. The issue is 4.4.2 and the original way we (ROM devs) had to implement superuser.
There are two routes to take to keep from losing root. The easiest for most users is to turn off auto updates and not to update superuser (app or binaries). The second is more difficult for the average user. Do a complete removal of superuser and install the latest.
I suggest the first way for everyone. It is simple and fool proof.
Sent from my XT1045 using XDA Free mobile app
jlmancuso said:
The actual issue is not superuser or the updates. The issue is 4.4.2 and the original way we (ROM devs) had to implement superuser.
There are two routes to take to keep from losing root. The easiest for most users is to turn off auto updates and not to update superuser (app or binaries). The second is more difficult for the average user. Do a complete removal of superuser and install the latest.
I suggest the first way for everyone. It is simple and fool proof.
Sent from my XT1045 using XDA Free mobile app
Click to expand...
Click to collapse
As always, thanks for your response. Your recommendation is what I've been doing, just wanted to follow-up on this and see if there was anything else I needed to consider or change as well.
My main concern was to make sure I was not going to run into any "big" issues (especially security) by staying on current version. Thanks for explaining where the issue really lies on this too. I'm obviously not a dev, however I do want to understand what is exactly going on and responses like yours always provide that type of info. :good: Thank you.
And, FWIW, using "fool proof" to describe a process only makes me more curious (and no, not in that way) about your suggestion. :laugh:
Now I HAVE to find out more about that option... (only after some of the best BBQ in all of the land - Sugarfire BBQ in STL )
jlmancuso said:
The actual issue is not superuser or the updates. The issue is 4.4.2 and the original way we (ROM devs) had to implement superuser.
There are two routes to take to keep from losing root. The easiest for most users is to turn off auto updates and not to update superuser (app or binaries). The second is more difficult for the average user. Do a complete removal of superuser and install the latest.
I suggest the first way for everyone. It is simple and fool proof.
Sent from my XT1045 using XDA Free mobile app
Click to expand...
Click to collapse
How do you disable auto update of binary on SuperSU? I keep seeing it in the notification bar, very annoying.
see #5 for problem
Hi guys,
so after quite some time with custom Roms I decided to go stock again as somehow I don't need root at all. Well, that's not true. I miss AdAway.
As there is no possibility to root the stock rom, is there ANY AdBlocker that works on Lollipop? AdBlock Plus doesn't (yet).
Why did you say there is no possibility to root the stock rom ?
I'm running Stock ROM, rooted and AdAway running fine.
ckpv5 said:
Why did you say there is no possibility to root the stock rom ?
I'm running Stock ROM, rooted and AdAway running fine.
Click to expand...
Click to collapse
How do you root the stock rom? I couldn't find out how.
Can I root without losing my data?
fBx said:
How do you root the stock rom? I couldn't find out how.
Can I root without losing my data?
Click to expand...
Click to collapse
Flash twrp recovery and root through the recovery. It'll ask you when you reboot the system if you want to root it
Sent from my HTC One_M8 using XDA Free mobile app
Huh. Didn't know it was THAT straightforward and I've been flashing my phones for years.
Well. I flashed TWRP and SuperSU 2.46, succeeded. But Adaway and Adfree don't work correctly. They block the ads but only until you reboot, then it's reverted, kinda like with a tethered jailbreak on iPhones.
What am I doing wrong here? Also the block is not like on KitKat - there it was really blocked, really removed, here only the images of the ads are removed but you still see the space they were supposed to be.
I also used a system app removal tool that also didn't work although it shows success. It just removes the installed data like updates.
When I delete apps manually via ES Explorer, they just reappear at the next reboot.
Root Checker says root is fine but it isn't supposed to behave like that and undo my changes.
What's wrong? Do I need another kernel maybe? As I said I went back to stock completely and updatet through to L.
I believe I got whats causing the issue.
After deleting a system app and rebooting, I got a message saying that the phone was restored from an "unnormal behaviour". Does Lollipop bring some kind of system restore point that just automatically restores itself when "weird" things like host file alteration happens? If yes, how do I get rid of that?
This phone has always had system files protected since KitKat. You need a kernel mod to delete system apps.
Don't know why the ad blockers aren't working. Adaway is working fine for me on stock US Dev Edition rooted. You said you are using Adaway and AdFree? Are you actually using both at the same time? maybe they are interfering with each other?
No I meant it happens with both. Only use adaway now. They work but after a reboot the adblock is gone and I need to apply it again. In fact, AdAway says it's deactivated and AdFree says it's already up to date but ads show anyway and I need to install the fix again to get rid of them.
Can you maybe point me to a kernel mod? Would want to get rid of some bloatware.
Maybe I should try installing xposed and see if it's gone after a reboot.
fBx said:
Can you maybe point me to a kernel mod? Would want to get rid of some bloatware.
Click to expand...
Click to collapse
The thread is here: http://forum.xda-developers.com/showthread.php?t=2701816
But unfortunately, flar2 hasn't had the time to update for LP. A user posted the kernel module in Post #210, but a subsequent user said it doesn't work. Custom ROMs have write protection disabled, as does Dev Edition stock ROM.
fBx said:
No I meant it happens with both. Only use adaway now. They work but after a reboot the adblock is gone and I need to apply it again. In fact, AdAway says it's deactivated and AdFree says it's already up to date but ads show anyway and I need to install the fix again to get rid of them.
Click to expand...
Click to collapse
Odd, as mentioned, I've used AdAway for quite some time now, and don't have these issues.
Yes, very odd indeed. Well, if I don't get it sorted out somehow I might as well switch to Viper or some other close to stock custom Rom again, or make it Dev like you.
Things are getting worse, in 1 of 2 cases AdAway spits an error at me when trying to apply the fixes and the phone just reboots and undos everything. It's like some protection from rooting or changing anything although I am rooted. I don't understand it. I can't possibly be the only one having problems with root on Stock Lollipop
This is really annoying me. I think I'm better of just installing a custom rom and setting the phone up again, will cost me an hour but at least I'm done with the bugs.
Yup, decided to jump the gun, wipe and install ViperOne and now everything works as I wanted it to. AdAway stays active and working.
fBx said:
Yup, decided to jump the gun, wipe and install ViperOne and now everything works as I wanted it to. AdAway stays active and working.
Click to expand...
Click to collapse
Interesting. I wonder if Adaway is dependent on the system write protection being disabled. I wouldn't normally suspect that, and only thinking of it since you mentioned the system write protection issue as well.
On the other hand, its the only difference I can think of between my phone and yours that would matter. I am on stock rooted Dev Edition, which apparently does not have the system write protection enabled by default.
redpoint73 said:
Interesting. I wonder if Adaway is dependent on the system write protection being disabled. I wouldn't normally suspect that, and only thinking of it since you mentioned the system write protection issue as well.
On the other hand, its the only difference I can think of between my phone and yours that would matter. I am on stock rooted Dev Edition, which apparently does not have the system write protection enabled by default.
Click to expand...
Click to collapse
I also assume that's the reason. I've never been on a stock rom since I don't know when, but figured that actually I only wanted AdAway which would normally not require a custom rom per se... but as it didn't really work in the end (and also other root-requiring stuff), I went back to custom again. Well, it's not that it's that difficult to wipe the phone occasionally and set up a clean custom rom to get it back to perfect performance. Gonna go with it.
So, I'm new to rooting and this is my first Nexus device.
I'm loving it and all the options but now I'm getting a notification to update.
I see all the forums about hooking it up to a computer and using commands to do it all and then rerooting.
I was looking for an easier way.
I bought a Nexus 5 to play with because I liked this one so much and when OTAs came up, it would let me download them and reboot into CWM recovery and ask if I want to flash the ZIP.
This one just boots into TWRP (No CWM for 5x) and does nothing.
I found the update as a zip here:
<https://gist.github.com/jduck/744a6c8a9042e9c792b7>
My question is: can I just download it and use TWRP to flash it or is the sequence of commands on a computer the only way to do it?
Thank you in advance for your help and I apologize for my ignorance.
Gotta start somewhere though, right?
Hi !
I personnaly use NRT from Wugfresh for my Nexus 5x and my Nexus 7 2013, both rooted.
In "model type", select Nexus 5x and your build.
In "Restore/upgrade/downgrade", select "device is on/normal", then click "Flash stock+ unroot".
Select the build you want to install, it can dl and extract it for you, and select "No Wipe Mode" in order to keep your data and apps. (don't try to put your ota file here)
Go through the steps, and in the end, hit "Root" to root again.
I know there are others methods to apply just the OTA with command lines, but I never did it cause I never took the time to learn. I should do it, maybe it's faster with command lines.
Anyway this works, even if it takes a little time, and it is kind of automatic. But I strongly recommend you try both method to find what suits you most. Or wait for someone else to reply so you'll have more points of view !
Have fun with your N5x !
I like the idea of that.
Does it reinstall the superuser app automatically?
If so, which one?
And does it redo custom recovery?
And which one for that?
Sorry for all the questions but I purchased SuperSU and I don't want it to automatically download a different one and have to go through the steps to change a superuser app.
erichjelm said:
I like the idea of that.
Does it reinstall the superuser app automatically?
If so, which one?
And does it redo custom recovery?
And which one for that?
Sorry for all the questions but I purchased SuperSU and I don't want it to automatically download a different one and have to go through the steps to change a superuser app.
Click to expand...
Click to collapse
Use chainfires "flashfire" for this process
http://www.xda-developers.com/flashfire-updated-with-android-6-0-and-ota-support/
Darke5tShad0w said:
Use chainfires "flashfire" for this process
http://www.xda-developers.com/flashfire-updated-with-android-6-0-and-ota-support/
Click to expand...
Click to collapse
It's not working.
I have Xposed installed.
I unmarked all modules, rebooted, and tried again but to no avail.
Other than Xposed, no mods to the kernel.
erichjelm said:
I have Xposed installed.
I unmarked all modules, rebooted, and tried again but to no avail.
Other than Xposed, no mods to the kernel.
Click to expand...
Click to collapse
Are you using flashfire v0.28?
Xposed modifies the system so while you maybe able to get the ota it can prevent you from installing them even with flashfire.
Go to the flashfire thread and see if this is a problem with the app or because or xposed (most likely answer).
Otherwise find the ota threads and see if you can flash it through recovery (not the N version)
Yeah, it's that version of Flashfire.
I have the update zip but I'm afraid to just flash it.
I was hoping that I'd get some more help here.
Not that I don't appreciate your help.
Thank you, by the way.
erichjelm said:
Yeah, it's that version of Flashfire.
I have the update zip but I'm afraid to just flash it.
I was hoping that I'd get some more help here.
Not that I don't appreciate your help.
Thank you, by the way.
Click to expand...
Click to collapse
Thats at the end of my ability to help you with this particular problem, I have only owned a Nexus for 2 months and they are completely diff to Samsung plus I run pure nexus rom, you may just have to use a computer.
And I really appreciate it.
I'll just use a computer and do it.
Don't want to risk trying to flash the zip and bricking but I'm still curious.
Just not curious enough.
Haha.
Got it.
In case anyone needs to know for themselves, I wanted to post it here.
http://nexus5.wonderhowto.com/how-t...thout-losing-root-no-computer-needed-0168428/
I used that and it worked.
I didn't flash the Xposed zip and had to later on.
Worth it just to add it to the queue to save the time.
Everything else seems to be working fine thus far.
A few settings are changed (TinyCore was turned off and hidden apps in Smart Launcher 3 were unhidden) but that's nothing big.
erichjelm said:
Got it.
In case anyone needs to know for themselves, I wanted to post it here.
http://nexus5.wonderhowto.com/how-t...thout-losing-root-no-computer-needed-0168428/
I used that and it worked.
I didn't flash the Xposed zip and had to later on.
Worth it just to add it to the queue to save the time.
Everything else seems to be working fine thus far.
A few settings are changed (TinyCore was turned off and hidden apps in Smart Launcher 3 were unhidden) but that's nothing big.
Click to expand...
Click to collapse
That is the same manipulation I explained in post 2, but with Flashfire, without using a computer. And full automated, where with nrt you have to factory reset and root later. I'll try it next time ! And yeah, the version of SuperSu is always the latest, and if it is not, it will update via play store (I bought it as well ^^)
Greedybro said:
That is the same manipulation I explained in post 2, but with Flashfire, without using a computer. And full automated, where with nrt you have to factory reset and root later. I'll try it next time ! And yeah, the version of SuperSu is always the latest, and if it is not, it will update via play store (I bought it as well ^^)
Click to expand...
Click to collapse
This one didn't unroot. Just uninstalled Xposed. Kept all my data and stuff. Apps stayed signed in even. I was afraid because I heard "factory reset" in yours. Or something to that nature. The only thing I'm having problems with now is Tapatalk told me to check my adblock settings and won't load anything. I'll have to look up what's wrong with it. Other than that, it's doing all right.
You are right and wrong, it unroots but reroots in the process. Same I did when I used nrt. And as i didn't wipe data, apps stayed sign in as Well.
But i tried flashfire on my nexus 7 and I it is way more useful and faster than nrt. I am adopting it !
Anyone running Android Q beta 2 ? Can you make a comparison to Pie in terms of speed or apps that crash or hang? TIA
I have no apps crashing and no apps unable to start. Performance and battery are identical to Pie.
The Android Q is definitely a daily driver for me.
EDIT: The only single issue I have is that double-tap or lift to wake are not working.
Guys how to root? Android Q?
hfmls said:
Guys how to root? Android Q?
Click to expand...
Click to collapse
Install TWRP. Flash Magisk (canary). Reboot into system. Instal Magisk Manager. Reboot and done.
Will this work on beta 2 ??
spleenandcigars said:
Install TWRP. Flash Magisk (canary). Reboot into system. Instal Magisk Manager. Reboot and done.
Click to expand...
Click to collapse
not work on Beta 2, bro
How best to backout of the AndroidQ beta2?
Installed but Android Auto is playing up so want to go back to v8
Can't mount system partition R/W on Marlin using TWRP 3.2.3-1 once updated to AQB2 (although I did a dirty update by removing the -w erase flag from the bat file before executing.) Guess I'll try nuking everything and rebuilding from scratch to see if the partitions will mount R/W to install Magisk...
Is anyone able to set his own mp3 ringtone on this?
hfmls said:
Guys how to root? Android Q?
Click to expand...
Click to collapse
I'm using this.
https://forum.xda-developers.com/showpost.php?p=79271368&postcount=1282
George_Bushels said:
I'm using this.
https://forum.xda-developers.com/showpost.php?p=79271368&postcount=1282
Click to expand...
Click to collapse
Good Information:
Does it work with Android Q beta DP2 patch (marlin-qpp2.190228.023-factory-c262576d.zip)?
Homeboy76 said:
Good Information:
Does it work with Android Q beta DP2 patch (marlin-qpp2.190228.023-factory-c262576d.zip)?
Click to expand...
Click to collapse
Yes.
sonpro10x said:
not work on Beta 2, bro
Click to expand...
Click to collapse
As you can see in this screenshot, it's working just fine. You have to install the latest Magisk canary build. TWRP won't work to do some backups, but you can flash it fine.
Been running Q2 for a few days and is a great daily driver. As soon as Nova paid was installed I have no complaints
and battery life has been excellent. Coming from the Essential phone rooted this has been a pleasant surprise. For 180.00 new
unlocked on Sprint this is a good deal. I also prefer the 16x9 screen and camera.
So, I have some weirdness going on…
I screwed up and tried to install the last P build after getting the ota beta Q update….i had issues (possibly of my own making).
Realized that trying to go back wasn’t going to work so I thought I would just reinstall the Q beta version 2, I downloaded it…all seemed well until I wanted to get to “settings”
I can pull the “curtain’ down and see a few quick access icons (wifi, Bluetooth, airplane mode…) but it won’t pull farther down (second swipe) to see other options and the “settings” gear at the top. I also don’t seem to be getting notifications, I hear them but don’t see an icon.
I also can’t get to the setting that allow me to transfer files.
Any ideas?
Edit: also can't get to my app drawer...
Edit 2: home button doesn't work either...
I got it, it must have been a bad "dirty flash", did a clean install, and all is working as expected...except,
I've got root but can't see my internal storage with ES file explorer (I can see it when using my PC) (or any other root explorer) and can't edit my build.prop (can't save it)
tufyuma said:
So, I have some weirdness going on…
I screwed up and tried to install the last P build after getting the ota beta Q update….i had issues (possibly of my own making).
Realized that trying to go back wasn’t going to work so I thought I would just reinstall the Q beta version 2, I downloaded it…all seemed well until I wanted to get to “settings”
I can pull the “curtain’ down and see a few quick access icons (wifi, Bluetooth, airplane mode…) but it won’t pull farther down (second swipe) to see other options and the “settings” gear at the top. I also don’t seem to be getting notifications, I hear them but don’t see an icon.
I also can’t get to the setting that allow me to transfer files.
Any ideas?
Edit: also can't get to my app drawer...
Edit 2: home button doesn't work either...
I got it, it must have been a bad "dirty flash", did a clean install, and all is working as expected...except,
I've got root but can't see my internal storage with ES file explorer (I can see it when using my PC) (or any other root explorer) and can't edit my build.prop (can't save it)
Click to expand...
Click to collapse
I did a clean flash, and had the same issue with the internal storage. It was weird though because chrome couldnt see it either, and kept failing to get permission to store files. Doing another Wipe now to try and resolve it...
bonfire62 said:
I did a clean flash, and had the same issue with the internal storage. It was weird though because chrome couldnt see it either, and kept failing to get permission to store files. Doing another Wipe now to try and resolve it...
Click to expand...
Click to collapse
Please let us know if it works....I hardly ever use my hot spot, but it's nice to know I have it for emergencies!
tufyuma said:
Please let us know if it works....I hardly ever use my hot spot, but it's nice to know I have it for emergencies!
Click to expand...
Click to collapse
Wasn't talking about hotspot specifically.... The issue with Chrome is still there, still not able to download anything, as it pops up that it needs permission, I hit continue...and nothing. It normally gives the permission request notification here, but it does not.
bonfire62 said:
Wasn't talking about hotspot specifically.... The issue with Chrome is still there, still not able to download anything, as it pops up that it needs permission, I hit continue...and nothing. It normally gives the permission request notification here, but it does not.
Click to expand...
Click to collapse
Right, I don't think I've tried to download anything with chrome, I want the permissions so I can edit the buildprop file.
Having just checked, I also cannot download anything using chrome, Opera doesn't seem to have a problem, though. I didn't check any other browsers
tufyuma said:
Right, I don't think I've tried to download anything with chrome, I want the permissions so I can edit the buildprop file.
Having just checked, I also cannot download anything using chrome, Opera doesn't seem to have a problem, though. I didn't check any other browsers
Click to expand...
Click to collapse
After clean flash, still having the same issue with the downloads. Going to Solidexplorer shows that the sdcard partition never created a Download folder. Chrome also is completely not working now, so definitely rolling back until it's resolved.