Related
Does anybody know how to fix this? On the bottom left where you get notifications, my machine is showing a round circle of small circles, like a loading timer. I click on it and under notifications, it says Ongoing, Loading Data, Please Wait... 12:22 AM. It looks like something is caught up. It's not hindering me from doing anything, but something in some small place must be a little out of whack.
Also, whenever I plug in my NC with my USB into my mac, iPhoto is opening up. It never did that before I did some of the other modifications last night.
I have a rooted NC that I then went and enabled multitouch. I also installed su and the Superuser app. I went through the process to be able to use live wallpapers. I then installed the stuff to get weather apps working.
Here's what I have installed total to see if anything here might be the problem. I'd hate to have to unroot and start over, but will if need be. All I'd really lose is my progress in angry birds and who really cares about that.
com.ccpcreations.android.MarioLiveWallpaprer.apk
com.brilliantintent.notes.apk
com.levelup.beautifulwidgets.apk
org.adw.launcher.apk
com.chains.apk
com.slideme.sam.manager.apk
com.aws.android.elite.apk
com.starvingmind.android.livewallpaper.apk
com.levelup.beautifullive.apk
mobi.mgeek.TunnyBrowser.apk
com.studydroid.flashcards.apk
com.rovio.angrybirds.apk
net.andforge.wallpaper.heartMonitor.apk
com.facebook.katana.apk
org.openintents.notepad.apk
com.noshufou.android.su.apk
com.geteit.android.wobble.demo.apk
com.rovio.angrybirdsseasons.apk
berserker.android.livewallpapers.waterize.apk
A bunch of the live wallpapers are going to get removed as either they don't work well or I just don't like them. I've just started playing with the ones I found.
Any help with either a process of finding out what's causing this hanging notification or a solution would be greatly appreciated. Thanks.
mad5427 said:
Does anybody know how to fix this? On the bottom left where you get notifications, my machine is showing a round circle of small circles, like a loading timer. I click on it and under notifications, it says Ongoing, Loading Data, Please Wait... 12:22 AM. It looks like something is caught up. It's not hindering me from doing anything, but something in some small place must be a little out of whack.
Also, whenever I plug in my NC with my USB into my mac, iPhoto is opening up. It never did that before I did some of the other modifications last night.
I have a rooted NC that I then went and enabled multitouch. I also installed su and the Superuser app. I went through the process to be able to use live wallpapers. I then installed the stuff to get weather apps working.
Here's what I have installed total to see if anything here might be the problem. I'd hate to have to unroot and start over, but will if need be. All I'd really lose is my progress in angry birds and who really cares about that.
[long list of stuff installed on the nook removed]
A bunch of the live wallpapers are going to get removed as either they don't work well or I just don't like them. I've just started playing with the ones I found.
Any help with either a process of finding out what's causing this hanging notification or a solution would be greatly appreciated. Thanks.
Click to expand...
Click to collapse
In general, if you have a an issue that began after installing some stuff, you should uninstall things until the ssue is resolved and then reinstall the other stuff. Then you can focus on the one apk that seems to have caused the issue.
Thanks for the response. I tried that and couldn't figure it out so I flashed back to the original software. Some file somewhere got gummed up somehow. Who knows.
When I just rerooted a little bit ago, I timed things wrong and the root wasn't.....right, I guess. I could install and uninstall apps, but I got a $ when I typed adb shell instead of #. Something was 1 and not 0. I didn't do it right and didn't have true root.
So, back to square one. I now have it rooted correctly and am one by one going through the steps to gain further access to function. I'm only doing one thing at a time, testing it, making sure everything is good and then I move on.
If I get any type of error again, I'll know exactly what I was doing and hopefully the cause.
Im not really sure if this a theming question or a developing question since I dont know if this is something done with code or not. But I was wondering if its possible to blur backgrounds when a pop up window is in the foreground. I see that it does this when I power down or reboot the phone. I think it would look cool if it did this for all pop up windows. Ive also seen a video where some guys phone did this. If I find the video again, I'll post the link.
EDIT: Found the video. It shows what Im talking about at the 30 second mark.
http://www.youtube.com/watch?v=5GAx41jRjiY
Noticed none of the current builds have the CRT animation enabled, thought I'd share how to turn it on. Please note that it is at times a bit buggy. For me it works about 8 out of 10 times.
What it is:
Note: 1 - This will work on any device and on any version of Android back to GB. (Obviously the Nexus specific tools wont work on anything other than the Nexus)
Note 2 - You will have to redo this every time you update your rom.
Here's the quick rundown -
First, you'll have to pull the framework-res.apk from your tablet.
This can be done via adb, but the easiest way would be to either use WugFresh's Nexus Root Toolkit or mskips Google Nexus 7 TOOLKIT.
When asked what file to pull, type in "/system/framework/framework-res.apk" (without quotes)
Once you have that pulled, install this tool: http://forum.xda-developers.com/showthread.php?t=1432152
Follow the directions on how to use it in the thread.
Once you have decompiled the apk, you'll want to edit the "files-to-edit\framework-res.apk\res\values\bools.xml" file.
The value you want to change in the bools value is the "<bool name="config_animateScreenLights">true</bool>" change "true" to "false". I reccommend downloading Notepad++ to edit.
Make sure you save it. Once saved, recompile the apk using the tool you install, then create an update zip (I renamed mine to crtanimation.zip for ease).
Reboot into recovery, flash the zip, clear cache, reboot.
Tada!
Krunk_Kracker said:
Noticed none of the current builds have the CRT animation enabled, thought I'd share how to turn it on. Please note that it is at times a bit buggy. For me it works about 8 out of 10 times.
Here's the quick rundown -
First, you'll have to pull the framework-res.apk from your tablet.
This can be done via adb, but the easiest way would be to either use WugFresh's Nexus Root Toolkit or mskips Google Nexus 7 TOOLKIT.
When asked what file to pull, type in "/system/framework/framework-res.apk" (without quotes)
Once you have that pulled, install this tool: http://forum.xda-dev...d.php?t=1432152
Follow the directions on how to use it in the thread.
Once you have decompiled the apk, you'll want to edit the "files-to-edit\framework-res.apk\res\valuesbools.xml" file.
The value you want to change in the bools value is the "<bool name="config_animateScreenLights">true</bool>" change "true" to "false".
Make sure you save it. Once saved, recompile the apk using the tool you install, then create an update zip (I renamed mine to crtanimation.zip for ease).
Reboot into recovery, flash the zip, reboot.
Tada!
Click to expand...
Click to collapse
"Once you have that pulled, install this tool: http://forum.xda-dev...d.php?t=1432152"
This link is not working.
TahrirSquare said:
"Once you have that pulled, install this tool: http://forum.xda-dev...d.php?t=1432152"
This link is not working.
Click to expand...
Click to collapse
Apologies.
Fixed now
Why would someone want to do this?
Guardsix said:
Why would someone want to do this?
Click to expand...
Click to collapse
Why would someone want to put a custom rom on N7?
Sent from my Nexus 7 using Tapatalk 2
They most likely don't know what CRT animation is, NOT why they might want to make changes to the system.
Nothing in the OP provides a hint as to what that is or what it does. To be honest, I'm not sure I know what it is. A quick search shows that it is enabled in a lot of ROMs but not what it actually is or does.
Sent from my Nexus 7
krelvinaz said:
They most likely don't know what CRT animation is, NOT why they might want to make changes to the system.
Nothing in the OP provides a hint as to what that is or what it does. To be honest, I'm not sure I know what it is. A quick search shows that it is enabled in a lot of ROMs but not what it actually is or does.
Sent from my Nexus 7
Click to expand...
Click to collapse
OK, makes sense, I was assuming most knew what it meant.
I'll make a quick video.
Just made a video, uploading it.
krelvinaz said:
They most likely don't know what CRT animation is, NOT why they might want to make changes to the system.
Nothing in the OP provides a hint as to what that is or what it does. To be honest, I'm not sure I know what it is. A quick search shows that it is enabled in a lot of ROMs but not what it actually is or does.
Sent from my Nexus 7
Click to expand...
Click to collapse
If you don't know what it is then you obviously haven't flashed many roms and therefore should probably not even attempt this...
Thanks OP and sry for the ungrateful ones here.
updated OP with a demo vid
I guess the CRT animation is more obscure than I thought.
Okay... I get it... It enables animation effects when turning the device off, rather than just blanking the screen.
I get the same effect turning on and off with
https://play.google.com/store/apps/details?id=com.soulfulz.android.turnoffscreen
You can select from a number of effects, sounds for both when the device is turned on and off via the button. You have to hit the button for it to do it, but for the risk of modifying system files, this is easy and safe to do.
krelvinaz said:
Okay... I get it... It enables animation effects when turning the device off, rather than just blanking the screen.
I get the same effect turning on and off with
https://play.google.com/store/apps/details?id=com.soulfulz.android.turnoffscreen
You can select from a number of effects, sounds for both when the device is turned on and off via the button. You have to hit the button for it to do it, but for the risk of modifying system files, this is easy and safe to do.
Click to expand...
Click to collapse
Except your solution is wakelock city on top of having to enable it as a device administrator. Sounds like you also have to hit the shortcut or use the app itself to get the desired effect versus it being naturally accomplished when hitting the power button/screen timeout. And if it doesn't work in ICS, not sure it will work on JB.
krelvinaz said:
Okay... I get it... It enables animation effects when turning the device off, rather than just blanking the screen.
I get the same effect turning on and off with
https://play.google.com/store/apps/details?id=com.soulfulz.android.turnoffscreen
You can select from a number of effects, sounds for both when the device is turned on and off via the button. You have to hit the button for it to do it, but for the risk of modifying system files, this is easy and safe to do.
Click to expand...
Click to collapse
My way is easy and safe to do, if you follow the direction.
All your doing is turning something on. It's something that Google intended to be toggled.
Krunk_Kracker said:
My way is easy and safe to do, if you follow the direction.
Click to expand...
Click to collapse
Something users of XDA are so good at doing? Reading and following instructions.
All your doing is turning something on. It's something that Google intended to be toggled.
Click to expand...
Click to collapse
Curious, they didn't implement it in their flagship first tablet and first official device to have Jelly Bean?
BTW, I am not knocking you, just have a lot of experience dealing with users that don't read, can't follow instructions...
The info on extracting and the tool was good reading, I just know a lot of users that will botch this up and start posting BRICKED threads.
Via my HTC Rezound
krelvinaz said:
Something users of XDA are so good at doing? Reading and following instructions.
Curious, they didn't implement it in their flagship first tablet and first official device to have Jelly Bean?
BTW, I am not knocking you, just have a lot of experience dealing with users that don't read, can't follow instructions...
The info on extracting and the tool was good reading, I just know a lot of users that will botch this up and start posting BRICKED threads.
Via my HTC Rezound
Click to expand...
Click to collapse
I'm sorry if people are unable to follow direction, but honestly that's not my problem.
If they mess it up, it wont brick, and if it does, all they have to do is dirty flash their rom and it's fixed.
I asked the question "Why" because it seems a lot of trouble just to see your device (N7, in this case) turn off. I've done a great deal of modding to my ICS devices, but haven't really found much reason to mod a JB device. I know there are tons of boot animations which make your device really different when turned on, but having CRT just for turning off your device seems a waste of time.
Of course, this is only my opinion and I'm glad you figured out how to do this, but I still don't understand why!
Guardsix said:
I asked the question "Why" because it seems a lot of trouble just to see your device (N7, in this case) turn off. I've done a great deal of modding to my ICS devices, but haven't really found much reason to mod a JB device. I know there are tons of boot animations which make your device really different when turned on, but having CRT just for turning off your device seems a waste of time.
Of course, this is only my opinion and I'm glad you figured out how to do this, but I still don't understand why!
Click to expand...
Click to collapse
Why not?
To sound cliche, Android is all about options.
I present you with yet another modding option.
Sent from my Nexus 7 using Tapatalk 2
I'm not really understanding the animosity with this simple mod...
Neat! I am sure that I will get around to this eventually but I am surprised that I haven't noticed that there was no CRT animation enabled already.
Sent from my Nexus 7 using xda app-developers app
Guardsix said:
I asked the question "Why" because it seems a lot of trouble just to see your device (N7, in this case) turn off. I've done a great deal of modding to my ICS devices, but haven't really found much reason to mod a JB device. I know there are tons of boot animations which make your device really different when turned on, but having CRT just for turning off your device seems a waste of time.
Of course, this is only my opinion and I'm glad you figured out how to do this, but I still don't understand why!
Click to expand...
Click to collapse
Don't understand why you don't just switch to an iphone
Ok I tried what the OP has posted but the compiler tool is borked, no way to recompile the file after editing the file. Read over the original posting and found that the issue is still not fixed, any other way to do this??
i rooted my kindle, and so most games i download work now. But all Voltage Inc. games wont. They all pop up a web page saying they know I'm on a kindle. I've fixed it so they cant see my kindle is rooted and my id is shown as a fake one, but it still catches im on a kindle.
Is there a way to hide or change it so my Kindle just shows up as an Android phone to apps?
Would some terminal emulator code work for that?
Also, i cant for the life of me get my background and lock screen to change.
I'm using ADW launcher and tried themes for it but no difference.
I got my kindle as a present awhile back from someone who said they got it from a pawn shop (lol) so i don't know if that makes a difference. Its a second generation one, i figured that out when i was trying to mess with the ADB for ways to change the background... anddd at some point with my messing with it, its decided not to let me pull the notification bar down anymore and when i turn it horizontal the screen is black like ADW doesn't readjust.
Please help i know i should be happy with how far I've gotten but its too much fun to try and mess with it, you know? Modding is a little addictive.
don't be too harsh on me if you think i deserve criticism for my noobness.:crying:
technoeve said:
i rooted my kindle, and so most games i download work now. But all Voltage Inc. games wont. They all pop up a web page saying they know I'm on a kindle. I've fixed it so they cant see my kindle is rooted and my id is shown as a fake:fingers-crossed: one, but it still catches im on a kindle.
Is there a way to hide or change it so my Kindle just shows up as an Android phone to apps?
Would some terminal emulator code work for that?
Also, i cant for the life of me get my background and lock screen to change.
I'm using ADW launcher and tried themes for it but no difference.
I got my kindle as a present awhile back from someone who said they got it from a pawn shop (lol) so i don't know if that makes a difference. Its a second generation one, i figured that out when i was trying to mess with the ADB for ways to change the background... anddd at some point with my messing with it, its decided not to let me pull the notification bar down anymore and when i turn it horizontal the screen is black like ADW doesn't readjust.
Please help i know i should be happy with how far I've gotten but its too much fun to try and mess with it, you know? Modding is a little addictive.
don't be too harsh on me if you think i deserve criticism for my noobness.:crying:
Click to expand...
Click to collapse
First off,no one gets harsh for noobness here. We all help each other.
And now about your question. I would suggest flashing a custom ROM like CM instead of Amazon OS. But if you want to keep it stock rooted,try editing the build prop.
SafinWasi said:
First off,no one gets harsh for noobness here. We all help each other.
Click to expand...
Click to collapse
You sir, deserve a cookie
And to the OP, I remember a while back that there was an app for KFHD users that would allow us to change a setting temporarily to get different Play Store apps to work with our devices. I'll scrounge around and see if I can find it.
Ph0enix_216 said:
You sir, deserve a cookie
And to the OP, I remember a while back that there was an app for KFHD users that would allow us to change a setting temporarily to get different Play Store apps to work with our devices. I'll scrounge around and see if I can find it.
Click to expand...
Click to collapse
Thanks mate ?
And yeah,it's called market helper
Sent from my device running CyanogenMod 11
Found it, here's the link:
http://forum.xda-developers.com/showthread.php?t=2146216
Hi there, easiest way is to change your build prop. This requires root and you don't need to flash roms etc but I recommend this if you want the "full" android experience. Ask me how to change build prop first if you are interested. If you change the build prop you can spoof your apps into thinking that your device is a different device. However it is quite safe ONLY IF YOU DO IT CORRECTLY. hope this helps!
I have an issue with the action pill on the bottom of the screenshot attached. Absolutely ignoring the context of the The huge contextual pill on top of my search bar, I seem to get those for a lot of the services I trigger which is fine, it's normal. My issue is they stay on the screen for a really really long time.they last several seconds to almost a minute.
Does anyone know how to reduce the time for those or why that may be happening? Has anyone else faced this issue with their pixel devices specifically? I don't seem to have this issue with my Samsung note 10 plus.
If anyone can provide clarity for me on this I really would appreciate it because it's starting to get annoying lol thank you!
https://github.com/samchugit/Immersive_Gestural_Nav_Bar
Use this module or can be found in magisk app.
The pill is there to avoid the accidentally touch navigation gesture.
keaheng said:
https://github.com/samchugit/Immersive_Gestural_Nav_Bar
Use this module or can be found in magisk app.
The pill is there to avoid the accidentally touch navigation gesture.
Click to expand...
Click to collapse
My apologies I should have been more clear I'm not talking about the tiny pill on the very bottom for navigation I meant that big white contextual overlay on top of my search bar with the contextual text.
Why it is there doesn't bother me it's just that it's there for 30 seconds to a minute sometimes I'm wondering if anybody's been able to come across how to fix that.
plus I don't know how to root my device nor I'm able to learn based off I need tutorials that have been posted so rooting is not an option sadly.
thepersona said:
My apologies I should have been more clear I'm not talking about the tiny pill on the very bottom for navigation I meant that big white contextual overlay on top of my search bar with the contextual text.
Why it is there doesn't bother me it's just that it's there for 30 seconds to a minute sometimes I'm wondering if anybody's been able to come across how to fix that.
plus I don't know how to root my device nor I'm able to learn based off I need tutorials that have been posted so rooting is not an option sadly.
Click to expand...
Click to collapse
Roots super easy on these as long as you can OEM unlock.
Assuming so install the magisk app, pull boot.img from your factory image, patch it with magisk (it will end up in your download folder as magisk_patched.img) and flash it. Boom, wham, pow.
madscribblerz said:
Roots super easy on these as long as you can OEM unlock.
Assuming so install the magisk app, pull boot.img from your factory image, patch it with magisk (it will end up in your download folder as magisk_patched.img) and flash it. Boom, wham, pow.
Click to expand...
Click to collapse
Thanks for the simplification, I gotta figure out if my device can oem unlock. It's an unlocked device purchased in Canada.
This is what I was talking about in my original post. Ignoring why it's there, or it's context. I know why those pop up. My complaint is that they are there for 30 sec to a minute in length. Why does my device do that. It's been getting annoying. Cause other devices I own have the same contextual pill but don't stay for as long as they do on my P4xl
thepersona said:
Thanks for the simplification, I gotta figure out if my device can oem unlock. It's an unlocked device purchased in Canada.
This is what I was talking about in my original post. Ignoring why it's there, or it's context. I know why those pop up. My complaint is that they are there for 30 sec to a minute in length. Why does my device do that. It's been getting annoying. Cause other devices I own have the same contextual pill but don't stay for as long as they do on my P4xl
Click to expand...
Click to collapse
That's definitely not normal behaviour. Could be caused by one of your apps hogging resources and slowing down your phone.
But if it's not that, maybe try a Factory Reset?
thepersona said:
Thanks for the simplification, I gotta figure out if my device can oem unlock. It's an unlocked device purchased in Canada.
This is what I was talking about in my original post. Ignoring why it's there, or it's context. I know why those pop up. My complaint is that they are there for 30 sec to a minute in length. Why does my device do that. It's been getting annoying. Cause other devices I own have the same contextual pill but don't stay for as long as they do on my P4xl
Click to expand...
Click to collapse
Fair. I thought I'd help on root, albeit a tangent.
What you're seeing is not normal. Have you tried a third party launcher like Nova?
madscribblerz said:
Fair. I thought I'd help on root, albeit a tangent.
What you're seeing is not normal. Have you tried a third party launcher like Nova?
Click to expand...
Click to collapse
Much appreciated! And yes I explicitly transfered everything fr pixel launcher on to Nova. I am explicitly using nova as it adds much more freedom and customization, as well as integration with sesame.
But that pop up always pops up in Spotify or files or anything giving me context on what I've done wether I've deleted something, updates a playlist, moved a photo, etc. So I know it's supposed to be there whenever it show up.
The issue is that it should not last longer than like 5 seconds max. And on my device it's 20 seconds or even longer especially when moving Giles around in device storage etc, it's a while before it goes away and has become annoying lol.
madscribblerz said:
Fair. I thought I'd help on root, albeit a tangent.
What you're seeing is not normal. Have you tried a third party launcher like Nova?
Click to expand...
Click to collapse
Plus with regard to root I figure I'm better off waiting until my device is no longer supported because if I root now, it's going to be like going through hell and back trying to get monthly updates or feature drops flashing this flashing that.
that whole procedure seems very tedious and filled with a lot of leg work. And not only am I dumb but I'm also lazy LOL so I hope in three years time rooting a device namely p4xl will become foolproof. Lol
But I might have the spine to delve into it once the p4xl isn't supported by Google
thepersona said:
Much appreciated! And yes I explicitly transfered everything fr pixel launcher on to Nova. I am explicitly using nova as it adds much more freedom and customization, as well as integration with sesame.
But that pop up always pops up in Spotify or files or anything giving me context on what I've done wether I've deleted something, updates a playlist, moved a photo, etc. So I know it's supposed to be there whenever it show up.
The issue is that it should not last longer than like 5 seconds max. And on my device it's 20 seconds or even longer especially when moving Giles around in device storage etc, it's a while before it goes away and has become annoying lol.
Click to expand...
Click to collapse
Not an exact answer, given, but that is a toast message that you're dealing with. You may want to look for options on how to modify the default behavior for toast messages. It likely requires root to modify but if you can do so then that's where it'll be. you may want to look in the settings for the apps where it displays to see if there is some kind of toast notification option to disable.
---------- Post added at 07:41 PM ---------- Previous post was at 07:39 PM ----------
thepersona said:
Plus with regard to root I figure I'm better off waiting until my device is no longer supported because if I root now, it's going to be like going through hell and back trying to get monthly updates or feature drops flashing this flashing that.
that whole procedure seems very tedious and filled with a lot of leg work. And not only am I dumb but I'm also lazy LOL so I hope in three years time rooting a device namely p4xl will become foolproof. Lol
But I might have the spine to delve into it once the p4xl isn't supported by Google
Click to expand...
Click to collapse
It is kind of foolproof, but does require a few manual steps each time you update. Do know that Google does not void the warranty for devices that are rooted.
Personal preference I respect, but I wouldn't let technical obstacles overcome your desire to root at some point. It's actually very simple compared to other devices I've had including the earlier pixels, so if all things are equal the Pixel 4 is the easiest to deal with.
madscribblerz said:
Not an exact answer, given, but that is a toast message that you're dealing with. You may want to look for options on how to modify the default behavior for toast messages. It likely requires root to modify but if you can do so then that's where it'll be. you may want to look in the settings for the apps where it displays to see if there is some kind of toast notification option to disable.
I looked into the settings there's nothing on there specifically or explicitly talking about toast notifications. But that is a clearer answer I just can't seem to figure it out I thought it would have been notification dots but it's not that. Ah well lol
---------- Post added at 07:41 PM ---------- Previous post was at 07:39 PM ----------
It is kind of foolproof, but does require a few manual steps each time you update. Do know that Google does not void the warranty for devices that are rooted.
Personal preference I respect, but I wouldn't let technical obstacles overcome your desire to root at some point. It's actually very simple compared to other devices I've had including the earlier pixels, so if all things are equal the Pixel 4 is the easiest to deal with.
Click to expand...
Click to collapse
Yeah I agree with what you're saying and that's interesting I did not know that Google doesn't void the warranty if one decides to root their device. Thanks for the tidbit. Yeah I agree with you having a technical obstacle overcoming the desire right now is pretty high and it stings because if I knew I could do it in a way where I won't break my device or really mess it up that would have helped. I just recently learned about ADB and I haven't fully grasped the concept but I know enough to just get by lol.
If you know of a guaranteed method on how to root the Pixel 4 XL without damage to the device I would appreciate a link to a thread or even a video. Because everything that I've heard has been hit or miss everybody's gotten different results and potentially bricked or messed up their device there has been more mess ups then success and not been one guaranteed solution on how to root the device in a way where it wouldn't mess something up.
thepersona said:
If you know of a guaranteed method on how to root the Pixel 4 XL without damage to the device I would appreciate a link to a thread or even a video. Because everything that I've heard has been hit or miss everybody's gotten different results and potentially bricked or messed up their device there has been more mess ups then success and not been one guaranteed solution on how to root the device in a way where it wouldn't mess something up.
Click to expand...
Click to collapse
Ok,I'll give you a 101.
First unlock flashing. It's the same for all pixels and consists of 2 steps. The first is changing a setting under developer options (to enable developer options click the build number in about several times until you see it enable) and then toggle OEM unlock to enabled.
Step 2 is booting into fastboot mode (vol down while booting) and actually unlocking the phone (fastboot flashing unlock).
There are help files everywhere on that part so find one you like to get you through those steps. Again in this all pixels are equal, so don't stress if you can't find help for the 4 specifically. Note you do not need to unlock critical, and also note doing this will wipe your device. If you've done it right on startup you'll get a yellow warning screen (ignore).
The next part is rooting. Update your device to the latest factory image (boot in fastboot mode and run flash-all from the zip (remove the -w from the bat file if you don't want to wipe the phone).
Boot the phone after and let it run the ROM upgrade app. Install the magisk app and choose install and in the ROM image you downloaded is a boot.img file you will tell magisk to patch. Do so and in download you'll have a magisk_patched.img file. Move that to your computer, reboot into fastboot mode, and fastboot flash boot magisk_patched.img.
Reboot and you're in business.
I'll keep an eye on this thread and if you run into any problems I'll help you quickly. Also note you can't really destroy a pixel. There is a lot to cover to explain why (and I'm sure some creative soul has managed to) but you can always flash the factory ROM with the -w included in flash-all.bat to recover.
It is scary if you haven't done it, but if you're like me once you're rooted it was so easy you'll feel silly.
To update monthly download the ROM, extract boot.img, patch it with magisk, apply the ROM (no -w), reboot and let the ROM finish, reboot to fastboot mode, flash magisk_patched.img (like above), boot and all is good.
Any questions, just ask.
madscribblerz said:
Ok,I'll give you a 101.
First unlock flashing. It's the same for all pixels and consists of 2 steps. The first is changing a setting under developer options (to enable developer options click the build number in about several times until you see it enable) and then toggle OEM unlock to enabled.
Step 2 is booting into fastboot mode (vol down while booting) and actually unlocking the phone (fastboot flashing unlock).
There are help files everywhere on that part so find one you like to get you through those steps. Again in this all pixels are equal, so don't stress if you can't find help for the 4 specifically. Note you do not need to unlock critical, and also note doing this will wipe your device. If you've done it right on startup you'll get a yellow warning screen (ignore).
The next part is rooting. Update your device to the latest factory image (boot in fastboot mode and run flash-all from the zip (remove the -w from the bat file if you don't want to wipe the phone).
Boot the phone after and let it run the ROM upgrade app. Install the magisk app and choose install and in the ROM image you downloaded is a boot.img file you will tell magisk to patch. Do so and in download you'll have a magisk_patched.img file. Move that to your computer, reboot into fastboot mode, and fastboot flash boot magisk_patched.img.
Reboot and you're in business.
I'll keep an eye on this thread and if you run into any problems I'll help you quickly. Also note you can't really destroy a pixel. There is a lot to cover to explain why (and I'm sure some creative soul has managed to) but you can always flash the factory ROM with the -w included in flash-all.bat to recover.
It is scary if you haven't done it, but if you're like me once you're rooted it was so easy you'll feel silly.
To update monthly download the ROM, extract boot.img, patch it with magisk, apply the ROM (no -w), reboot and let the ROM finish, reboot to fastboot mode, flash magisk_patched.img (like above), boot and all is good.
Any questions, just ask.
Click to expand...
Click to collapse
Thanks brother I appreciate the guide and your patience in explains this and willing to help me out with this. The language and terminology I think is the most intimidating lol. I've got a MacBook pro so hopefully I can give this a shot and it will work with that device.
I'll keep you posted.
thepersona said:
Thanks brother I appreciate the guide and your patience in explains this and willing to help me out with this. The language and terminology I think is the most intimidating lol. I've got a MacBook pro so hopefully I can give this a shot and it will work with that device.
I'll keep you posted.
Click to expand...
Click to collapse
No worries
Only change with a Mac is the flash-all.bat I mentioned will be flash-all.sh.
thepersona said:
Much appreciated! And yes I explicitly transfered everything fr pixel launcher on to Nova. I am explicitly using nova as it adds much more freedom and customization, as well as integration with sesame.
Click to expand...
Click to collapse
I briefly tried Nova (but went back to Action Launcher) and I don't remember having that kind of problem. Did you have this problem before you switched to Nova?
fclifton said:
I briefly tried Nova (but went back to Action Launcher) and I don't remember having that kind of problem. Did you have this problem before you switched to Nova?
Click to expand...
Click to collapse
Nope not at all I think it occured after some update probably March.because it's been occurring to the point where I've noticed all throughout March I'm now updating to the April security patch so hopefully that will fix it
madscribblerz said:
No worries
Only change with a Mac is the flash-all.bat I mentioned will be flash-all.sh.
Click to expand...
Click to collapse
Hey man do I need to install any Google drivers onto a Mac apparently when I go to the website it says I don't need to but for rooting do I have to do that?
And do I just Google how to fast boot flash a pixel or something in order to get the zip folders you talked about?
Is this walkthrough in the video below the same as the method youre describing? Cause I can't seem to find any guides on how to do that method.
thepersona said:
Hey man do I need to install any Google drivers onto a Mac apparently when I go to the website it says I don't need to but for rooting do I have to do that?
And do I just Google how to fast boot flash a pixel or something in order to get the zip folders you talked about?
Is this walkthrough in the video below the same as the method youre describing? Cause I can't seem to find any guides on how to do that method.
Click to expand...
Click to collapse
That is a much more detailed guide to the approach that I'm describing. I think following it you'll be able to do it without issue. It's the same approach I've been using for months with no issues. I've even gotten so confident in it I don't even back up my phone before I update monthly. I just know things are going to work.
The zip folder comes from Google just search for Pixel 4 factory image and there will be a page with downloads of the most recent ROM files. April was just released yesterday. That's the file that you want to download and will have the boot.img in it.
I'm not certain on a Mac, but on a PC you have to download the USB drivers and then the platform tools from Google in order to have what you need to make this work. But I think the guide you're referring to will be able to give you that stuff.
---------- Post added at 06:25 PM ---------- Previous post was at 06:01 PM ----------
thepersona said:
Hey man do I need to install any Google drivers onto a Mac apparently when I go to the website it says I don't need to but for rooting do I have to do that?
And do I just Google how to fast boot flash a pixel or something in order to get the zip folders you talked about?
Is this walkthrough in the video below the same as the method youre describing? Cause I can't seem to find any guides on how to do that method.
Click to expand...
Click to collapse
The ROM site is https://developers.google.com/android/images
I figured out my original issue on this post. It was in accessibility, the setting was called time to take action timeout! Now it's fixed. The bloody toast notification is back to default!
thepersona said:
I figured out my original issue on this post. It was in accessibility, the setting was called time to take action timeout! Now it's fixed. The bloody toast notification is back to default!
Click to expand...
Click to collapse
Awesome news. I learned something so win-win. :good: