Click here :
link1; https://drive.google.com/file/d/1B22rs0c-yndeokbHApTY_u9UKkM_5S3k/view?usp=drivesdk
link2: https://mega.nz/#!uUAE3bBK!RAtnbYOXpSQXbWocOLbFYZHU4rOmcUStLgcNs1mPkn8
Every now and then, every rooted Android user faces this issue that while they try to activate some apps that involve security, they get a message saying that they can’t use the app because their phone is rooted. It’s good that they face it. It shows how strict Google’s security is. But on the other hand, it’s annoying too because we can’t use such apps .E.g. Most of the banking apps. Those apps are required frequently but rooted users can’t use it because their activation doesn’t complete.
Other example does include Google’s Tez. While activation Tez gives the error as below.
Your device is not passing Security checks.
Here’s how you solve the issue and get such apps working on rooted devices.
Let me know your difficulties and FAQ in the comment section below. Feel free to mail me your detailed problems at mjadhav570@gmail.com or you can start discussing at FAQ section “FAQ“.
Note: As rooted android devices are assumed to be not trusted, all these apps don’t work, Installing Magisk just hides the root from apps or android security layer thus allowing you to bypass the security checks and making app work on your device. By no way, this thing is secure.
Did you remember those days where we had those CRT monitors in which picture used to get displayed with continuously emitting rays onto the display? Crazy technologies no?
Now recently few of the smartphones are exhibiting screen burn in issue. CRT and recent AMOLED display technologies are totally different technologies but screen burn in issue is been seen on both kind of displays.
Basically few things on our mobile display like navigation bar, status bar, Always ON display, wallpaper for that matter…these things are always there on the display, Display pixels(LED’s) in those portion of the screen are always been powered ON and OFF in order to display the stuff.
This continuous burden of displaying same stuff again and again causes some display pixels to retain the previous data for long time. This results in retention of information over the display for long time.
Now note here down that although this thing is called “Screen burn in” issue, there no actual burning over screen or any part of the screen. Its called so because the pixels exhibiting this behavior look like burnt in.
Here is one of the screens with this issue.
This doesn’t even happen instantly but on few models, it’s seen to happen after few months of usage. On the other hand this issue might be a serious issue if you don’t have first aid for it .
Well how to prevent your screen from this effect?
Here are general tips . Basically preventing screen burn has to do with preventing same pixels begin lit up again and again.
Android Oreo has recently been released an is been ported for few devices. I’ll be writing an article soon on “How you backup not only the apps but the whole Android ” so that while flashing your phone, or for some reason if your phone goes off, if in case it gets soft broken, you an restore it as is.
But here’s the thing with such Backup and Restore in Android Oreo. If you backup Android Oreo ROM that has fingerprint or pin or password set for lock-screen ( Everyone’s phone has one of these now a days) using one of the recoveries like TWRP and CWM, It’s probably not gonna get restored and you won’t be able to unlock your device after restore which makes it completely unusable.
So how do you solve it ?
Here’s the steps for this.
Note: Your phone needs to be rooted in order for this trick to work.
Let me know your difficulties and FAQ in the comment section below. Feel free to mail me your detailed problems at mjadhav570@gmail.com or you can start discussing at FAQ section “FAQ“.
Have a good day :-). Peace !!!
Playing with the actual processors and programming them to behave the way you wanted isn’t as easy as you think it is. Those who have been cross compiling ROMS by themselves or those who dare to flash custom ROMS into their phone would definitely know the extent of the efforts required for developing ROMS, apps for your android device.
It’s very usual that you mess up with your phone while flashing ROMS or configuring kernel etc. Here are some tips to quickly recover from such situations. I’ll be listing down more as I go on learning new ones.
Phone not turning ON just notification light blinks:
Stay tuned. This is just part 1. I’ll be posting more soon.
Let me know your difficulties and FAQ in the comment section below. Feel free to mail me your detailed problems at mjadhav570@gmail.com or you can start discussing at FAQ section “FAQ“.
Have a good day :-). Peace !!!
First of all , let’s talk little about recovery…you should know that.
Have you ever observed your phones storage? If it’s 64 GB storage, usable memory you get isn’t that much. Its usually about 52,55 GB. Where does the other space go?
Its used by Android system by itself . The whole compiled code of android system installed in your phone is kept there. It isn’t kept directly as is into it but there are some partitions made and specific code is placed in specific partition.
One of those partitions is recovery partitions. Its usually responsible for flashing your phone, resetting it, erasing other partitions etc a piece of code which wakes up recovery partition during phones restart and helps to perform all operations/responsibilities of recovery partitions is called “recovery”.
TWRP(Team Win Recovery Project) and CWM(Clock Work Mod) are both examples of those piece of code..
So as you know little about recoveries, let’s now go ahead and see how do you backup and restore using TWRP and CWM.
Note: installing TWRP/CWM requires that your phones bootloader is unlocked. Follow article “How to unlock bootloader of your mobile device” for unlocking it.
How to back up android partitions using TWRP/CWM:
adb reboot bootloader
fastboot flash recovery <path to downloaded recovery>
adb reboot recovery
Let me know your difficulties and FAQ in the comment section below. Feel free to mail me your detailed problems at mjadhav570@gmail.com or you can start discussing at FAQ section “FAQ“.
Have a good day :-). Peace !!!
Let’s see bootloader concept quickly first. You should know that…
When you turn ON your mobile device, it can’t directly start loading android system. It needs to be woken up step by step. E.g. First it checks if the device hardware is working fine or not, then starts loading something called as kernel etc etc.
So one the section in this waking up process is “Bootloader”. There are other sections, partitions too such as Recovery, Data, System etc.
These bootloaders now a days, for security reasons, come locked by OEM so that they can’t be modified without permission. and thats wat we need to unlock in order to allow us to install recovery into our phone or to install custom ROM.
There are few tings you need to consider before you think of Unlocking bootloader.
With that said, let’s go with the steps to unlock bootloader of any android device.
Now I understand that I took this pretty straight forward but unlocking bootloader is little different for different OEMS. So can’t publish the universal method.
Let me know your difficulties and FAQ in the comment section below. Feel free to mail me your detailed problems at mjadhav570@gmail.com or you can start discussing at FAQ section “FAQ“.
Have a good day :-). Peace !!!
So here we go.
Most obvious thing, you need to take backup of your phone first in order to restore it onto another.
Usual backup apps doesn’t take the real backup. They just backup apps. They don’t keep any app specific data such as your game score, your app settings etc. And that’s the catch. Let’s see how do you backup apps with data so that you won’t need to worry about setting the device again and that headache of installing the apps again.
Here are the steps :
Now as the backup is complete, go to TWRP/CWM respective folder using any file manager app and find a folder called backup there and transfer the whole to the new device that you wanna restore. This backup is useful in case you reset your device. You can restore it as it is without worrying about downloading apps again and without worrying about setting the whole stuff again.
To restore this backup into another device, make sure that the phone model is same, backup taken on one device absolutely won’t work on other. Don’t even try it, it will brick your device and it won’t ever wake up. Use article “How to restore backups using custom recoveries in android“ .
So once you copy backup to new device, follow same above steps, unlock your target device, install same custom recovery, and restore using recovery options.
Cool! you are done. Restart your phone and that’s it.. Your target device get restored exactly same as the source one. You can use the same method one the source device too. In case you reset your phone, you can restore the same backup again on the same device to restore it back to the previous state.
Let me know your difficulties and FAQ in the comment section below. Feel free to mail me your detailed problems at mjadhav570@gmail.com or you can start discussing at FAQ section “FAQ“.
Have a good day :-). Peace !!!
Hey,
We are so happy to see you back here again. WE are setting up “My Android Page” and will be back with whole redesigned experience, lot of exciting articles and more fun ..
Thank you so much for being a part of My Android Page community…
– Mukesh