Hello there,
i am from India.
i tried to use hffc bank's new app.
but it doesnt support rooted device.
i tried magisk, but its unable to hide root from the app.
so, i tried magisk uninstaller to remove root from my phone.
now, root checker says root is not properly installed.
and the hdfc app says its rooted.
i am stuck between these two.
please help. i want to complete remove root and use banking app.
Stock rom or Custom?
Flash default boot.img of your current rom.
pradeeppk said:
Stock rom or Custom?
Flash default boot.img of your current rom.
Click to expand...
Click to collapse
custom ROM.
currently aosp extended.
Related
I had already rooted my phone and have TRWP (Maclaw's) installed. Actually, I am running CM 12.1. But I wanna go back to stock!
But I have some questions:
Where can I download a stock (preferably updated to 4.1.2) ROM?
My device is already rooted, but will I need to flash with SuperSU to give the stock ROM root functionality?
How can I delete Samsung (e.g. ChatON) and Google bloat (e.g. Google+, Hangouts) that comes with the stock ROM?
wtx1033 said:
I had already rooted my phone and have TRWP (Maclaw's) installed. Actually, I am running CM 12.1. But I wanna go back to stock!
But I have some questions:
Where can I download a stock (preferably updated to 4.1.2) ROM?
My device is already rooted, but will I need to flash with SuperSU to give the stock ROM root functionality?
How can I delete Samsung (e.g. ChatON) and Google bloat (e.g. Google+, Hangouts) that comes with the stock ROM?
Click to expand...
Click to collapse
Don't be lazy & use search bar next time. Most of your questions are already answered. Anyway see here & here.
Hello everyone,
I'm having an issue - I wasn't able to flash the newest extracted firmware in the development section so I went ahead and just ran the full RUU. I've been running custom roms for years and I decided that maybe I just wanted to run stock rooted for a while so I unlocked my bootloader again, flashed the most recent TWRP and installed the most recent SuperSU zip.
Unfortunately it does not seem to have rooted my phone. SuperSU is indeed installed in the system folder and it prompts for root permission when I use root apps, but even when I grant permission the apps cannot obtain root access. What happens is it looks like they are going to get root access, the phone slows down a bit for a second, and then I get an error message from the app in question saying that either my phone isn't rooted or that root permission has been denied. If I open SuperSU, it lists all of my root apps with the green hashtag indicating that permission is granted.
Am I correct in assuming that installing SuperSU did not root my phone? If so, is there a way to root without installing a custom rom?
For clarification, this is all on the most recent RUU, software version 6.23.651..10, Lollipop 5.0.2
Thanks in advance.
Which version of SuperSU are you flashing?
Sloth said:
Which version of SuperSU are you flashing?
Click to expand...
Click to collapse
Well I'm a dolt, I was using v1.69 but now I see that is a very old version. Going to try 2.46 right now, thanks.
Edit: Same issue on 2.46 :/
For anyone still looking at this thread, I was able to achieve root by flashing the newest SuperSU, version 2.52 which is actually still in beta and therefore not offered if you go to the main portion of the SuperSU website.
SuperSU v2.65 is the current stable offering
I used CF Auto Root a while back to root my Nexus 6 (months ago). It did the trick getting the bootloader unlocked and rooting the phone. I then proceeded to install TWRP and then installed Pure Nexus. From then to know the phone has been a joy to use. This ROM is fantastic.
Recently I decided to look into custom Kernels, Elementalx is the one I have been reading up on. I installed the kernel, and then purchase the EX Kernel Manager. Using the app I realized that the phone wasn't rooted, or so it told me. I test this with the Root Checker Basic App and it confirmed that the phone was not rooted.
I am not sure what happened but what I wanted to do was run the SuperSU zip via TWRP again, but wanted to ask you guys if this would be an issue. I can't see why it would but it Rooth had already been achived and then it was gone so..... I just wanted to ask in case.
Sorry that this was a little long winded. Thanks in advance.
Magisk and SuperSU achieve root without modifying the system partition through patching of the kernel's ramdisk (?). When you installed the new kernel it installed an unpatched copy. This is why you lost root.
Download SuperSU from the XDA thread and flash it in TWRP to restore root.
Strephon Alkhalikoi said:
Magisk and SuperSU achieve root without modifying the system partition through patching of the kernel's ramdisk (?). When you installed the new kernel it installed an unpatched copy. This is why you lost root.
Download SuperSU from the XDA thread and flash it in TWRP to restore root.
Click to expand...
Click to collapse
Thanks for the quick reply. That makes sense. I will run SuperSU again. Take care.
Hello i want to use Magisk but failed. It said that i need original boot.img to continue. Before it i installed twrp from Miui Forum that have a working touchscreen and then rooted it using latest super su.
Is anyone have original boot.img from latest stable global rom? Or is there any way to install magisk? I need to use root cloack for my banking app.
dirty flash ur rom and will have a clean boot image to work with magisk.... anyway root cloak not work anytime... i got same issue with latest HSBC app.... i try everything to HIDE but seems not work !
lesscro said:
dirty flash ur rom and will have a clean boot image to work with magisk.... anyway root cloak not work anytime... i got same issue with latest HSBC app.... i try everything to HIDE but seems not work !
Click to expand...
Click to collapse
So we still dont have any solution for banking app? I rooted my device to get rid of thermal throttle
u need try before give up ! Actually no solution work with my bank but maybe with ur bank, you will have more luck than me !
I have an unlocked bootloader with TA-Backup like described in this thread.
But to get my banking app working I only want ro use the stock kernal.
I use the newest firmware: G8441_47.2.A.10.28_1310-4373_R3C
Is it possible to install AdAway if I boot with a different kernal with root and activate the host files?
After a reboot the stock kernal will be used with working adaway.
Does this work?
DripleX said:
I have an unlocked bootloader with TA-Backup like described in this thread.
But to get my banking app working I only want ro use the stock kernal.
I use the newest firmware: G8441_47.2.A.10.28_1310-4373_R3C
Is it possible to install AdAway if I boot with a different kernal with root and activate the host files?
After a reboot the stock kernal will be used with working adaway.
Does this work?
Click to expand...
Click to collapse
Better option for you on that situation is to use a dns proxy for ad filtering
something like this app
https://f-droid.org/en/packages/org.jak_linux.dns66/
Yes I use a app like this, but the problem is, that sometimes it takes up to 1 - 2 min till it is connected to the DNS Server.
Have you tried if the banking app works with magiskhide and "hide magisk package name" from magisk settings?
vofferz said:
Have you tried if the banking app works with magiskhide and "hide magisk package name" from magisk settings?
Click to expand...
Click to collapse
Yes, I tried this, but as I read in some other threads, this will only work with newest Magisk.
But then I have to recompile the kernal for myself.
@DripleX, If you like to check if magisk is causing your (banking) apps to detect root, you may try this:
j4nn said:
Dear @albenex, although I would also assume it should be possible to resolve this with use of magiskhide and other settings, I've uploaded not-pre-rooted kernels for the latest fw version into my experimental folder here.
So you can clean up all traces of magisk (factory reset may be needed to be sure) and use a boot-*-47.2.A.10.45-hideunlock.img kernel to test it. Also be sure to run unmodified stock fw.
Click to expand...
Click to collapse
These kernels are not pre-rooted with magisk but include the patch to hide bootloader unlock.
That should provide you setup very close to still locked phone (if you have your TA-locked restored).
If the app is working with the *-hideunlock.img kernel, magisk would need to be made hidden to get it working with a rooted kernel.
If it did not work even with the not-prerooted kernel, it would mean BL unlock is detected some other way (most likely using your Android Attest key - assuming you have it "provisioned") as it seems to be the case with google pay.
A donation was received on Tue Apr 30 15:03:03 UTC 2019 - I assume it has been from you @DripleX.
If so, thank you.
Thank you @j4nn for your reply!
I will check this after my vacation.
And yes, I made the donation