Develop Bugs

OTA updates after debloating

I have read several threads on debloating this device, including this really good one: http://forum.xda-developers.com/galaxy-tab-s/help/debloating-t2805503 . The info there that eliminating split-screen capability should be most useful!
However, I don't have enough experience to find the answer to my question from what I have read. If I use any of the relevant root tools to de-crap the machine, or if I just root, will I lose the ability to receive OTA updates? If so, is there any way to apply them short of waiting for someone to come out with a new ROM?
Is freezing with Titanium safe for this purpose, since nothing is removed? Or do I need to save the old stock ROM, and reload it, do the update, and then re-root and re-freeze everything?
Thank you for your indulgence, given that I'm sure that the answer is in several threads and I just don't know enough to identify it.

Root = no OTA, simple. Once an update comes out easiest thing to do is to download the new firmware from somewhere like Sammobile and flash using Odin, then re-root. Sammobile often releases the update before the OTA starts rolling out!
45 - Alba gu bráth

For titanium backup freezing just stops the apk from running and is safe because nothing is removed and when you install a new rom update, the things that were frozen will unfreeze since it requires root to freeze apps. Just follow what @killall said and that should do it. And if you root you can install twrp to backup your whole rooted rom as it was and restore back too it if you did something wrong while you were on the rooted rom.

killall said:
Root = no OTA, simple. Once an update comes out easiest thing to do is to download the new firmware from somewhere like Sammobile and flash using Odin, then re-root. Sammobile often releases the update before the OTA starts rolling out!
45 - Alba gu bráth
Click to expand...
Click to collapse
Doesn't flashing with Odin wipe data also, so it's not just simple re-rooting? Rooting doesn't prevent updating with Kies if I'm correct, does it matter whether you have custom recovery or not?

miloytyn said:
Doesn't flashing with Odin wipe data also, so it's not just simple re-rooting? Rooting doesn't prevent updating with Kies if I'm correct, does it matter whether you have custom recovery or not?
Click to expand...
Click to collapse
No, It should wipe the device's data.

I found a way to set my device status to official even though im rooted. Since I set the status to official I can check for updates without the custom software popup but I not tryed installing any updates since there are not any new updates atm.

kable said:
No, It should wipe the device's data.
Click to expand...
Click to collapse
I mean that of course it doesn't wipe your pictures and such, but flashing with Odin will wipe application data and restoring it from e.g. Titanium backup does take long time.

Here's hoping the custom ROM community picks up the slack and puts out a decent ROM this device sorely needs...

DUHAsianSKILLZ said:
I found a way to set my device status to official even though im rooted. Since I set the status to official I can check for updates without the custom software popup but I not tryed installing any updates since there are not any new updates atm.
Click to expand...
Click to collapse
What method did you use to root your Galaxy Tab S 8.4 SM-T705 LTE? And did you use CW or TWRP?

jadid said:
What method did you use to root your Galaxy Tab S 8.4 SM-T705 LTE? And did you use CW or TWRP?
Click to expand...
Click to collapse
I have a Galaxy tab s 10.5inch and rooted with cfautoroot and have twrp recovery installed. I used an xposed module called wanam xposed and changed my status to official. There is a ota update right now and Im scared to try the update becuase I dont know the risks. I have super su pro with survival mode on. Im not sure if its safe to do an ota update on rooted device as I dont want to brick it.

DUHAsianSKILLZ said:
I have a Galaxy tab s 10.5inch and rooted with cfautoroot and have twrp recovery installed. I used an xposed module called wanam xposed and changed my status to official. There is a ota update right now and Im scared to try the update becuase I dont know the risks. I have super su pro with survival mode on. Im not sure if its safe to do an ota update on rooted device as I dont want to brick it.
Click to expand...
Click to collapse
Thanks man, I followed your example and successfully rooted my device
What is xposed module called wanam xposed and what is it for?

jadid said:
Thanks man, I followed your example and successfully rooted my device
What is xposed module called wanam xposed and what is it for?
Click to expand...
Click to collapse
Yeah the module is wanam xposed and its for like customzing things such as hiding your carrier label and customize your lockscreen and nofications.

Do u know what the update changes?

OTA update! [SOLVED]

Hello guys,
today a new update appeared in my phone. It was a 107mb file for compatibility with gear and some stability updates(I though i did that update in the past).So I tried to install this. I downloaded but when the phone rebooted and started to install this it stack at 25% and error screen appeard. So I tried to install this from kies but kies says that I'm up to date. What's the problem? I have Belgian official firmware 4.4.2 kitkat rooted with xposed installed.
Sent from my GT-I9195 using XDA Free mobile app

has anyone else had this update? id like to know how can i get the update through OTA but i keep getting the "modified operating system"thing and i cant have this update :C

Black Swift said:
has anyone else had this update? id like to know how can i get the update through OTA but i keep getting the "modified operating system"thing and i cant have this update :C
Click to expand...
Click to collapse
I had the 'modified operating system' thing too.But i installed wanam xsposed and it has an option to check for 'fake' status.Now its official and i can get the updates.But the problem is that the update stops at 25%.Maybe it searching for an app that i deleted?Because i have deleted all the bloatware of samsung.Somenone can help?
EDIT:Kies today found the update.But the file is not 107mb like OTA is 800+.Why?
So my question now is if i do the update(via Kies3-the 800mb file) i will lose root?

So i did the update with kies.My data was not erased but i lost root.Now towerlroor say device currently not supported.So now how to root my s4 mini without tripping the knox bit?

Charlie said:
So i did the update with kies.My data was not erased but i lost root.Now towerlroor say device currently not supported.So now how to root my s4 mini without tripping the knox bit?
Click to expand...
Click to collapse
There is work around for that. First you must flash stock kernel from older kitkat firmwares like XXUCNF7 or CNE6 or CNH5.
This does not trip knox as you are flashing official kernel. Then you can use towelroot on the old kernel and after rooting and installing supersu , you can flash the new kernel. There is a thread in one of the sections that has stock kernel files for I9195. download one kernel and flash using odin. Good luck

sasank360 said:
There is work around for that. First you must flash stock kernel from older kitkat firmwares like XXUCNF7 or CNE6 or CNH5.
This does not trip knox as you are flashing official kernel. Then you can use towelroot on the old kernel and after rooting and installing supersu , you can flash the new kernel. There is a thread in one of the sections that has stock kernel files for I9195. download one kernel and flash using odin. Good luck
Click to expand...
Click to collapse
Thank you very much!
Sent from my GT-I9195 using XDA Free mobile app

sasank360 said:
There is work around for that. First you must flash stock kernel from older kitkat firmwares like XXUCNF7 or CNE6 or CNH5.
This does not trip knox as you are flashing official kernel. Then you can use towelroot on the old kernel and after rooting and installing supersu , you can flash the new kernel. There is a thread in one of the sections that has stock kernel files for I9195. download one kernel and flash using odin. Good luck
Click to expand...
Click to collapse
Is there a changelog for the updates of samsung?If yes where i can find it?

Charlie said:
Is there a changelog for the updates of samsung?If yes where i can find it?
Click to expand...
Click to collapse
Sammobile.com is the website. There you can find all samsung firmwares. Alternatively you can try samsung-updates.com
But I am not sure about change log.

Sorry

SOLVED: I leave this here so if anyone have the same question/problem go here.

Galaxy S4 Mini Plus (GT-I9195I) Hacking Guide (Root, Recovery, Xposed)

Trying to purchase Galaxy S4 Mini (GT-I9195) I received S4 Mini Plus (GT-I9195I) from online retailer. After some consideration I decided to treat this as a challenge and not to return the purchase. Here is what I learned so far about hacking this tiny piece of electronics:
Getting Root
I was not able to get root on the firmware installed on the phone (I9195IXXU1AOB1). The way I fixed that was to download another firmware from SamMobile and flashed it with Kies. The highest version I was able to flash without issues was I9195IXXU1AOD2, and it immediately updated to I9195IXXU1AOG1. For both versions latest KingRoot worked just fine. SuperSu Me fixed all the damage KingRoot did, replacing it with proper SuperSu. This did not trip Knox device status, BTW.
Flashing Custom Recovery
I downloaded official TWRP recovery from teamw.in and decided to go the hard way and install the recovery doing dd fom command line (ConnectBot) - I was hoping this will help me to keep the warranty. Worked just fine, but tripped Knox bit nevertheless. NB: avoid extra hassles and just use Odin to install recovery.
Installing Xposed
Xposed install sent my device into boot loop. Fixing permissions from recovery allowed me to boot, but gapps was having permanent ANRs. Upon investigation it looks like Xposed for KK is not designed to take selinux enforcing mode into account. Specifically it installed app_process with wrong security context making device unbootable. The fix is very simple:
1. Install Xposed Installer and ES File Explorer.
2. Open Xposed Installer, go to Framework menu, select "Recovery (write zip to SD card, flash manually)" Installation mode, press "Install/Update".
3. Open ES File, navigate to /sdcard/Andriod/data/de.robv.android.xposed.installer/files. There are two files there: Xposed-Installer-Recovery.zip and Xposed-Disabler-Recovery.zip
4. Now comes the fun part: in both archives you need to modify META-INF/com/google/android/update-binary: comment or delete all "chmod", "chown" and "restorecon" commands and replace "cp XXX/app_process[.orig] XXX/app_process" with "cat XXX/app_process[.orig] > XXX/app_process". This will keep both permissions and security context of the file. Unpack, edit, repack.
5. Reboot into recovery, install Xposed-Installer-Recovery.zip, enjoy.
I will send patch to Xposed maintainer later this week. But we have not seen new releases of Xposed fo KK for over a year now, so I am not sure it will get released any time soon.
I will update the post as my adventures continue - my plan is to have CyanogenMod on this device some day. Stay tuned.

Alte.78 said:
I will update the post as my adventures continue - my plan is to have CyanogenMod on this device some day. Stay tuned.
Click to expand...
Click to collapse
If you want you can PM me or join Freenode IRC and PM droidlambda. I've already started making CyanogenMod for the device, although I haven't come that far yet (even though the TWRP recovery you installed was ported by me). I could give you some advice (of my experiences with this phone and porting) and my basic config (which builds recovery successfully) if you want.

Does it have to go through all that trouble for Xposed? Or only if you want to install it via recovery (not classic / APK)?
Because recovery will trigger Knox (bye warranty).
Anyone installed Xposed the classic way on i9195i?

Alte.78 said:
Getting Root
For both versions latest KingRoot worked just fine. SuperSu Me fixed all the damage KingRoot did, replacing it with proper SuperSu.
Click to expand...
Click to collapse
If we install TWRP, can't we just flash SuperSU zip from recovery to avoid the KingRoot removal hassle?
Alte.78 said:
Installing Xposed
Xposed install sent my device into boot loop. Fixing permissions from recovery allowed me to boot, but gapps was having permanent ANRs. Upon investigation it looks like Xposed for KK is not designed to take selinux enforcing mode into account. Specifically it installed app_process with wrong security context making device unbootable.
Click to expand...
Click to collapse
Was this boot loop after classical (write to /system), or recovery install?
I installed Xposed classical on i9195 (not i) KK (it also has selinux enforcing) without problems. Is there a difference that I'm not aware of?
Thanks.

Alte.78 said:
Trying to purchase Galaxy S4 Mini (GT-I9195) I received S4 Mini Plus (GT-I9195I) from online retailer. After some consideration I decided to treat this as a challenge and not to return the purchase. Here is what I learned so far about hacking this tiny piece of electronics:
Getting Root
I was not able to get root on the firmware installed on the phone (I9195IXXU1AOB1). The way I fixed that was to download another firmware from SamMobile and flashed it with Kies. The highest version I was able to flash without issues was I9195IXXU1AOD2, and it immediately updated to I9195IXXU1AOG1. For both versions latest KingRoot worked just fine. SuperSu Me fixed all the damage KingRoot did, replacing it with proper SuperSu. This did not trip Knox device status, BTW.
Flashing Custom Recovery
I downloaded official TWRP recovery from teamw.in and decided to go the hard way and install the recovery doing dd fom command line (ConnectBot) - I was hoping this will help me to keep the warranty. Worked just fine, but tripped Knox bit nevertheless. NB: avoid extra hassles and just use Odin to install recovery.
Installing Xposed
Xposed install sent my device into boot loop. Fixing permissions from recovery allowed me to boot, but gapps was having permanent ANRs. Upon investigation it looks like Xposed for KK is not designed to take selinux enforcing mode into account. Specifically it installed app_process with wrong security context making device unbootable. The fix is very simple:
1. Install Xposed Installer and ES File Explorer.
2. Open Xposed Installer, go to Framework menu, select "Recovery (write zip to SD card, flash manually)" Installation mode, press "Install/Update".
3. Open ES File, navigate to /sdcard/Andriod/data/de.robv.android.xposed.installer/files. There are two files there: Xposed-Installer-Recovery.zip and Xposed-Disabler-Recovery.zip
4. Now comes the fun part: in both archives you need to modify META-INF/com/google/android/update-binary: comment or delete all "chmod", "chown" and "restorecon" commands and replace "cp XXX/app_process[.orig] XXX/app_process" with "cat XXX/app_process[.orig] > XXX/app_process". This will keep both permissions and security context of the file. Unpack, edit, repack.
5. Reboot into recovery, install Xposed-Installer-Recovery.zip, enjoy.
I will send patch to Xposed maintainer later this week. But we have not seen new releases of Xposed fo KK for over a year now, so I am not sure it will get released any time soon.
I will update the post as my adventures continue - my plan is to have CyanogenMod on this device some day. Stay tuned.
Click to expand...
Click to collapse
Thanks for the Xposed trick!
I managed to root according to your instructions (King root the supersu me), then install xposed through flashfire.
No need to flash custom recovery!
So knox is still 0x0!!
Great!

nick_white said:
Does it have to go through all that trouble for Xposed? Or only if you want to install it via recovery (not classic / APK)?
Because recovery will trigger Knox (bye warranty).
Anyone installed Xposed the classic way on i9195i?
Click to expand...
Click to collapse
Yes you have. Normal install (Write to /system) will send your phone into bootloop and you will have to re-flash your rom. I've tried that.

Karboush said:
Thanks for the Xposed trick!
I managed to root according to your instructions (King root the supersu me), then install xposed through flashfire.
No need to flash custom recovery!
So knox is still 0x0!!
Click to expand...
Click to collapse
Thats absolutely cool! I want to have custom recovery anyway, but your discovery will surely help a lot of people. :good:

nick_white said:
Was this boot loop after classical (write to /system), or recovery install?
I installed Xposed classical on i9195 (not i) KK (it also has selinux enforcing) without problems. Is there a difference that I'm not aware of?.
Click to expand...
Click to collapse
For me it failed both ways wiping out security context of app_process. Maybe your better luck has something to do with a different rom or Xposed version you are using?

Getting Root
I was not able to get root on the firmware installed on the phone (I9195IXXU1AOB1). The way I fixed that was to download another firmware from SamMobile and flashed it with Kies. The highest version I was able to flash without issues was I9195IXXU1AOD2, and it immediately updated to I9195IXXU1AOG1. For both versions latest KingRoot worked just fine. SuperSu Me fixed all the damage KingRoot did, replacing it with proper SuperSu. This did not trip Knox device status, BTW.
Could you point me as to where did you find the firmware for the phone. I'm tempted to try rooting it. Is xposed necessary for the root to take full effect or no ? Cause it sounds a bit tricky and risky.

CostasV23 said:
Could you point me as to where did you find the firmware for the phone.
Click to expand...
Click to collapse
Try this link: http://www.sammobile.com/firmwares/database/GT-I9195I/

soo
Alte.78 said:
Trying to purchase Galaxy S4 Mini (GT-I9195) I received S4 Mini Plus (GT-I9195I) from online retailer. After some consideration I decided to treat this as a challenge and not to return the purchase. Here is what I learned so far about hacking this tiny piece of electronics:
Getting Root
I was not able to get root on the firmware installed on the phone (I9195IXXU1AOB1). The way I fixed that was to download another firmware from SamMobile and flashed it with Kies. The highest version I was able to flash without issues was I9195IXXU1AOD2, and it immediately updated to I9195IXXU1AOG1. For both versions latest KingRoot worked just fine. SuperSu Me fixed all the damage KingRoot did, replacing it with proper SuperSu. This did not trip Knox device status, BTW.
Click to expand...
Click to collapse
So my phone has the AOD1 firmware can i root it like AOD2? Im in greece

Alte.78 said:
For me it failed both ways wiping out security context of app_process. Maybe your better luck has something to do with a different rom or Xposed version you are using?
Click to expand...
Click to collapse
Can you tell me if these will work for sure I have the aob1 firmware

Ok, so I have mine updated to I9195IXXU1AOG1. How do I get SuperSU on it without changing Knox to 0x1?

Which version of Xposed is everyone using? On the S4 Mini Plus?

xposed?
Is xposed necessary for the rooting process? or can i just skip it to avoid all the fuzz?

Alte.78 said:
Yes you have. Normal install (Write to /system) will send your phone into bootloop and you will have to re-flash your rom. I've tried that.
Click to expand...
Click to collapse
I upgraded my firmware to:
PDA: I9195IXXU1APA1
CSC: I9195IPHN1APA1
which is also (one of) the latest version, and has the Stagefright vulnerabilities fixed.
Then rooted with latest KingRoot (4.80) + Super Sume Pro.
Then installed Xposed 2.6.1 (stable) and installed "classical" (write to /system). It worked, no bootloops. Maybe you tried a different Xposed version?

Hi! anyone have a baseband I9195LUBUCNJ2?

Synomenon said:
Which version of Xposed is everyone using? On the S4 Mini Plus?
Click to expand...
Click to collapse
Im using the app_process 58 and
xposedBridge.jar 54 which i think is the latest stable edition as of 13/07/2016
Xposed installer version 2.61 with auto flash in recovery method no problems 5 months that i have it

Full debloat stock ROM on Samsung S4 mini Plus (GT-i9195i)
For more than a year, after I upgraded my firmware to:
PDA: I9195IXXU1APF1
CSC: I9195IYUX1APG1
which was the latest version from https://www.sammobile.com/firmwares/database/GT-I9195I/
I am using a debloat version of Galaxy S4 mini Plus (serranoveltexx). Inspired by @btnetro I made a script and tested a full debloat stock ROM on Samsung S4 mini Plus (GT-i9195i). All this time my device has worked very well and even now I am very pleased with him. For those who want to keep stock OS like me, I decided to share with you this flashable zip.
First flash via Odin, a custom recovery on your device( installation instructions here: https://forum.xda-developers.com/galaxy-s4-mini/development/recovery-cwm-twrp-philz-t3182207 ), restart your device and copy attached files in the root of your ext. SD card. Reboot your device in recovery mode and flash “Full_debloat_i9195i.zip”. For those who want to keep weather widget flash this file “weather2014_A3.zip” too (first debloat). Wipe /cache and reboot your device.

OK, i've a weird issue.
I tried all the available recoveries (Philz touch 6.59.0, twrp 2.8.4.0 & 2.8.7.1 etc, and all flashed with odin method) but none of them recognize my external SD.
I tried other sd cards as well, known to be good as they're used in other phones, but end up with th same.
Funny part is that inside os (stock KK 4.4.4) i can see all the files in SD card...
Any suggestion?

How to remove Root from Galaxy Tab S?

I bought a second hand Samsung Galaxy Tab S a few months ago and it has been working fine.
However, when I looked at version of Android then seems a bit old (5.0.2) and when I did a check for updates it said that it couldn't update because "The operating system on your device has been modified in an unauthorised way". When I checked then it seems that the device has been rooted.
A quick search suggested I should run SuperSU to remove the root. So, I had to download and install this, but, when I run it says "The SU binary needs to be updated. Continue?" - if I do then I get another message "If you have a custom recovery like TWRP or CWM that can be used to (try to) install the SU binary" and gives me a choice of Normal or TWRP/CWM. I am struggling to know how to proceed.
So, should it be possible to remove the root and still preserve all my data, apps, settings, etc?
If so, is SuperSu the way to go or are there other tools I should look at, such as Kingo Android Root?
Or, am I faced with rebuilding with a stock ROM?
Thanks

There is no update. 5.0.2 is the latest.

ashyx said:
There is no update. 5.0.2 is the latest.
Click to expand...
Click to collapse
OK, thanks for info.
However, I would still like to remove Root and would appreciate advice on this, please!

MysteryMan1 said:
OK, thanks for info.
However, I would still like to remove Root and would appreciate advice on this, please!
Click to expand...
Click to collapse
If your root manager is supersu then it has the option to unroot in it's settings.
Sent from my SM-T800 using XDA Premium HD app

3DSammy said:
If your root manager is supersu then it has the option to unroot in it's settings.
Sent from my SM-T800 using XDA Premium HD app
Click to expand...
Click to collapse
I've tried to fire up SuperSU, but, run into problems, as described in my initial post, and this is what I need to resolve.
Any ideas?

MysteryMan1 said:
... A quick search suggested I should run SuperSU to remove the root. So, I had to download and install this, but, when I run it says "The SU binary needs to be updated. Continue?" - if I do then I get another message "If you have a custom recovery like TWRP or CWM that can be used to (try to) install the SU binary" and gives me a choice of Normal or TWRP/CWM. I am struggling to know how to proceed.
...
Click to expand...
Click to collapse
I'm having a bit of trouble understanding the end goal. As stated Android v5.0.2 is the latest non-custom firmware available. As a previous owner has unlocked the bootloader and seems to have flashed a SuperSu version that modification is blocking any OTA update to v5.0.2. It is also clear your trying to avoid loosing user data.
Would it be acceptable to be rooted and use a different method to apply the latest Samsung stock firmware for your region? If the answer is yes install a TWRP recovery for your device model but you'll loose your warranty by tripping KNOX (you may already be in that state). Follow the instructions in the TabS TWRP thread.
Then finish the SuperSU install (where your stuck today). Then install Flashfire. With Flashfire and the downloaded latest Samsung firmware package you can flash the boot and system images to update your install then use ODIN to update the Bootloader image from that download firmware. You could also flash the recovery image but that would overwrite TWRP and in your case I don't see the point. Flashfire needs the whole Samsung firmware file to be available on the device itself unlike when using ODIN to flash the Bootloader image.
As I'm rooted but retained my warranty I use FlashFire and ODIN to update to the latest stock firmware and never loose user data. Unfortunately to root and not trip KNOX I did wipe my user data that first time so it does not seem to be an option for you.
Hope that gives you some ideas. In your current state it maybe as simple as completing the SuperSU install (assuming a custom recovery (TWRP/CM) is already installed) then using Flashfire and ODIN as described.
Good luck

3DSammy said:
I'm having a bit of trouble understanding the end goal. As stated Android v5.0.2 is the latest non-custom firmware available. As a previous owner has unlocked the bootloader and seems to have flashed a SuperSu version that modification is blocking any OTA update to v5.0.2. It is also clear your trying to avoid loosing user data.
Would it be acceptable to be rooted and use a different method to apply the latest Samsung stock firmware for your region? If the answer is yes install a TWRP recovery for your device model but you'll loose your warranty by tripping KNOX (you may already be in that state). Follow the instructions in the TabS TWRP thread.
Then finish the SuperSU install (where your stuck today). Then install Flashfire. With Flashfire and the downloaded latest Samsung firmware package you can flash the boot and system images to update your install then use ODIN to update the Bootloader image from that download firmware. You could also flash the recovery image but that would overwrite TWRP and in your case I don't see the point. Flashfire needs the whole Samsung firmware file to be available on the device itself unlike when using ODIN to flash the Bootloader image.
As I'm rooted but retained my warranty I use FlashFire and ODIN to update to the latest stock firmware and never loose user data. Unfortunately to root and not trip KNOX I did wipe my user data that first time so it does not seem to be an option for you.
Hope that gives you some ideas. In your current state it maybe as simple as completing the SuperSU install (assuming a custom recovery (TWRP/CM) is already installed) then using Flashfire and ODIN as described.
Good luck
Click to expand...
Click to collapse
Thank you for your very helpful and comprehensive reply. I can't profess to understanding all of it, but, I am sure I will get there eventually!
I shall follow your suggestion of trying to get get SuperSU installed first.
:good:

If you want to go back to stock just flash the latest firmware with odin.

Difference between firmware and ROM

Hello people how u doing
My question is what is the difference between firmware and ROM and the firmware available at Xiaomi firmware updater is safe or not.
I have rooted my phone with magisk, after using it i untooted it but still bhim app says root detected.
I know it depends upon safety net but other apps are working fine.
I want to ask did root made any changes to the firmware files,so that I flash the downloaded firmware file (around 59Mb) to get to my original firmware.
Also can i directly flash the firmware via recovery (orange fox).
I am currently on Pixel experience plus 9.0 (December patch version)
Please reply

Sidgup1998 said:
Hello people how u doing
My question is what is the difference between firmware and ROM and the firmware available at Xiaomi firmware updater is safe or not.
I have rooted my phone with magisk, after using it i untooted it but still bhim app says root detected.
I know it depends upon safety net but other apps are working fine.
I want to ask did root made any changes to the firmware files,so that I flash the downloaded firmware file (around 59Mb) to get to my original firmware.
Also can i directly flash the firmware via recovery (orange fox).
I am currently on Pixel experience plus 9.0 (December patch version)
Please reply
Click to expand...
Click to collapse
Root doesn't change your firmware. Aside from that i would recommend asking in a telegram group of any rom your going to flash of compatible firmware, and try not to flash different firmwares for 'performance' because it makes almost 0 difference.
Do be careful as there is this 'anti-roll back' [email protected]#t that you should consider before trying this. YouTube the phrase to find out what it is.