Develop Bugs

any marshmellow roms?

i want to buy this phone but cant live without xposed, so is there a 6.0 rom anywhere for this phone? ive looked but havent found anything

ncsuwolfs said:
i want to buy this phone but cant live without xposed, so is there a 6.0 rom anywhere for this phone? ive looked but havent found anything
Click to expand...
Click to collapse
Sultanxda and Arter97 CM MM Roms are still up im sure you can find a few others too
Edit: Opps sorry thought was OP3 thread :laugh:

ncsuwolfs said:
i want to buy this phone but cant live without xposed, so is there a 6.0 rom anywhere for this phone? ive looked but havent found anything
Click to expand...
Click to collapse
This phone launched with nougat. You can't run marshmallow on it.

liam_davenport said:
Sultanxda and Arter97 CM MM Roms are still up im sure you can find a few others too
Click to expand...
Click to collapse
where do i find those? (i have searched but can only find cm14 for pixel?
toknitup420 said:
This phone launched with nougat. You can't run marshmallow on it.
Click to expand...
Click to collapse
this is what i was afraid of....

ncsuwolfs said:
where do i find those? (i have searched but can only find cm14 for pixel?
this is what i was afraid of....
Click to expand...
Click to collapse
They do have magisk for this phone. I haven't used it but from what I've seen it's similar to xposed.

toknitup420 said:
They do have magisk for this phone. I haven't used it but from what I've seen it's similar to xposed.
Click to expand...
Click to collapse
I don't understand how it works but unless I misunderstood if you go to the official Magisk thread the creator claimed he was able to run Xposed with Magisk because his app prevented Xposed from needing to write anything to the system image. I supposed if you can't live without Xposed that would be worth looking into further.

There are no Marshmallow ROM's anywhere for this phone.
Never was, never will be.
Magisk isn't an Xposed replacement.
There is no replacement for Xposed.
Dammit, I miss my ~17 Xposed modules.
Most of which gave me options that you won't find on any custom Nougat ROM.

toknitup420 said:
They do have magisk for this phone. I haven't used it but from what I've seen it's similar to xposed.
Click to expand...
Click to collapse
It's a root option. As in you can run SuperSU or Magisk. Magisk has mods that can accomplish certain things that Xposed did but the majority of them don't work with the pixel so don't count on a suitable replacement.
jhs39 said:
I don't understand how it works but unless I misunderstood if you go to the official Magisk thread the creator claimed he was able to run Xposed with Magisk because his app prevented Xposed from needing to write anything to the system image. I supposed if you can't live without Xposed that would be worth looking into further.
Click to expand...
Click to collapse
The Magisk on pixel is supported by a guy that frequents the RR thread and he modded Magisk to work on the pixel so it's unofficial. Also there is NO Xposed for android n
---------- Post added at 11:55 PM ---------- Previous post was at 11:54 PM ----------
CZ Eddie said:
Magisk isn't an Xposed replacement.
Click to expand...
Click to collapse
This isn't completely true. There are Magisk mods that overlap things that Xposed was capable of. So depending on what you are trying to do and IF mods even worked for the pixel. It could be a replacement for some.

The Magisk on pixel is supported by a guy that frequents the RR thread and he modded Magisk to work on the pixel so it's unofficial. Also there is NO Xposed for android n
---------- Post added at 11:55 PM ---------- Previous post was at 11:54 PM ----------
Well that explains why on the official Magisk page the developer said he didn't know if there would ever be a working version for the Pixel phones but people are using Magisk anyway. Unfortunately Magisk seems to run into the same problems as SU on the Pixel in that it doesn't always install properly or maintain root if it does install--plus most Magisk modules don't work with the Pixel, which makes it much less functional than on other phones.

jhs39 said:
Well that explains why on the official Magisk page the developer said he didn't know if there would ever be a working version for the Pixel phones but people are using Magisk anyway. Unfortunately Magisk seems to run into the same problems as SU on the Pixel in that it doesn't always install properly or maintain root if it does install--plus most Magisk modules don't work with the Pixel, which makes it much less functional than on other phones.
Click to expand...
Click to collapse
I've been running magisk since 11.6 was dropped. I haven't had any issues keeping root or installing. Works every time and I flashing a new rom every 3 or 4 days.
Same with SU.
For magisk people keep leaving busy box in Magisk Manager turned on so it screws up root. It's in the magisk FAQ.

pcriz said:
I've been running magisk since 11.6 was dropped. I haven't had any issues keeping root or installing. Works every time and I flashing a new rom every 3 or 4 days.
Same with SU.
For magisk people keep leaving busy box in Magisk Manager turned on so it screws up root. It's in the magisk FAQ.
Click to expand...
Click to collapse
If you've been running SU for more than a few months on the Pixel then you know Google broke root on it and SU had to rewrite the app to fix the issue. That doesn't happen on other phones and is very likely intentional on the part of Google. At another point SU was suddenly causing problems and SU devs had to add a boot signature file to the flashing process. Again, this kind of thing doesn't happen with other phones. Pretending that SU and Magisk have always worked without problems on the Pixel is extremely misleading.

jhs39 said:
If you've been running SU for more than a few months on the Pixel then you know Google broke root on it and SU had to rewrite the app to fix the issue. That doesn't happen on other phones and is very likely intentional on the part of Google. At another point SU was suddenly causing problems and SU devs had to add a boot signature file to the flashing process. Again, this kind of thing doesn't happen with other phones. Pretending that SU and Magisk have always worked without problems on the Pixel is extremely misleading.
Click to expand...
Click to collapse
Lol why would I lie. I've been on magisk now since Feb. Tell me why I don't lose root?
Maybe you can't get it to work but that doesn't mean it doesn't work.
Also if you are following the evolution of things, signed builds are more secure. Root isn't broken you just have to resign the boot image because of HOW root is attained on the pixels.
Yes it only happens on the pixels because of the partition changes in the pixel. Since they have to be signed now with any bootloader from may and older, users need the verified boot signer.
But if you are paying five minutes worth of attention to all this you would know that all you have to do is flash the April bootloader and there is no longer a requirement for builds to be signed.
I've been through all this a million times. That said I'm still rooted like a champ.

Yeah for the pixel it's pretty straight forward, if you want to root use chainfire's zip it's 2.79 SR3, you're even advised on 2.82 that pixel users will not want to upgrade.
As far as the may bootloader situation, flash the april bootloader and you don't need to bother with the signing zip. Besides, I think dealing with knox was much worse

pcriz said:
Lol why would I lie. I've been on magisk now since Feb. Tell me why I don't lose root?
Maybe you can't get it to work but that doesn't mean it doesn't work.
Also if you are following the evolution of things, signed builds are more secure. Root isn't broken you just have to resign the boot image because of HOW root is attained on the pixels.
Yes it only happens on the pixels because of the partition changes in the pixel. Since they have to be signed now with any bootloader from may and older, users need the verified boot signer.
But if you are paying five minutes worth of attention to all this you would know that all you have to do is flash the April bootloader and there is no longer a requirement for builds to be signed.
I've been through all this a million times. That said I'm still rooted like a champ.
Click to expand...
Click to collapse
I've been paying a lot of attention to it actually. When you have to flash an old bootloader to prevent boot looping (which is what actually happens if you use the up to date bootloader) or you have to flash a boot signature file that wasn't previously needed then the flashing procedure suddenly changes again I wouldn't say it's easy to maintain root on a Pixel. I guess different people have different definitions for what easy is. As for Knox, I used to have many Samsung phones and once a procedure was figured out to get around it and root you were good for as long as you had the phone. With the Pixels Google seems to be actively trying to screw up apps that create root or bypass safety net via its monthly updates. It's a completely different situation in my opinion.

jhs39 said:
I've been paying a lot of attention to it actually. When you have to flash an old bootloader to prevent boot looping (which is what actually happens if you use the up to date bootloader) or you have to flash a boot signature file that wasn't previously needed then the flashing procedure suddenly changes again I wouldn't say it's easy to maintain root on a Pixel. I guess different people have different definitions for what easy is. As for Knox, I used to have many Samsung phones and once a procedure was figured out to get around it and root you were good for as long as you had the phone. With the Pixels Google seems to be actively trying to screw up apps that create root or bypass safety net via its monthly updates. It's a completely different situation in my opinion.
Click to expand...
Click to collapse
You went from saying "Magisk and SuperSU don't install properly or don't keep root" to talking about the changes to boot signing on newer bootloaders.
If you are going to share information at least try to be accurate. There is a whole slew of users in the development section running rooted ROMs just fine but if a new user reads your posts they will assume root is broken and flashing the pixel leads to boot loops.
You don't want to deal with the verified boot signer all you need to do is flash the april bootloader and reboot. It happens once. If that is too difficult then maybe those same people shouldn't bother flashing anything period.
No one said flashing and modding would be easy but flashing a bootloader ain't hard.

You might also want to take a look at the other threads in the Q&A which show people unable to flash TWRP, people boot looping when they flash TWRP, people unable to maintain root or flash custom Roms, etc. Even if you are able to maintain root like a pro there is plenty of very easy to find evidence from other people who don't have the same no problems experience as you.

jhs39 said:
You might also want to take a look at the other threads in the Q&A which show people unable to flash TWRP, people boot looping when they flash TWRP, people unable to maintain root or flash custom Roms, etc. Even if you are able to maintain root like a pro there is plenty of very easy to find evidence from other people who don't have the same no problems experience as you.
Click to expand...
Click to collapse
The only thing that proves is we have a ton of users that don't take the time to research.
You got users coming back from O that don't know they need an Android N bootloader in both slots to flash TWRP again.
You have users that are fastbooting ZIP files
You have users fastboot FLASHING TWRP
I read through those threads and in just about every case if you can't get recovery and root on the april boot loader it's probably user error. Welcome to XDA, it's the same on every device.
I guess all the guys that are rooted must full it. Or wizards or something.
I guess reading step by step directions makes me a wizard.

pcriz said:
I read through those threads and in just about every case if you can't get recovery and root on the april boot loader it's probably user error. QUOTE]
I answer these questions a lot and that is most certainly true.
Click to expand...
Click to collapse

pcriz said:
The only thing that proves is we have a ton of users that don't take the time to research.
You got users coming back from O that don't know they need an Android N bootloader in both slots to flash TWRP again.
You have users that are fastbooting ZIP files
You have users fastboot FLASHING TWRP
I read through those threads and in just about every case if you can't get recovery and root on the april boot loader it's probably user error. Welcome to XDA, it's the same on every device.
I guess all the guys that are rooted must full it. Or wizards or something.
I guess reading step by step directions makes me a wizard.
Click to expand...
Click to collapse
Actually that's absolutely not true. I came from a Nexus 6P. On the XDA threads for that phone there is an accurate, clear, up to date step by step guide on how to flash anything with that phone, including separate instructions for how to root, install a custom recovery, how to install a custom Rom and how to go back to stock. On the Pixels the threads are a complete free for all filled with confusing, contradictory and inaccurate information. I just read posts from earlier today from someone who is getting boot loops when flashing SuperSu. Not a single person responded by suggesting that he use the April bootloader. The suggested solution (which didn't work) was to flash the boot sig zip. How exactly is somebody supposed to research flashing on the Pixel when the XDA threads for this phone are a complete shambles? And since you are supposedly such an expert at flashing on this phone why don't you do something useful and help other people who are having problems instead of wasting everybody's time with your utterly pointless posts about how easy it is to flash on this phone and how people having trouble are idiots who didn't do their own research? You aren't simply part of the problem, dude--you are literally the personification of everything that is wrong with XDA.

jhs39 said:
.
Click to expand...
Click to collapse
This discussion ain't worth reading whatever it is you typed dude. I'm going to agree to disagree.
Sorry stable root is an unattainable unicorn for you. Sorry you're having such a difficult time. Sorry that making excuses for false information is a priority over finding out how it's actually done.
Happy flashing, best of luck to you sport.

Question about restoring system apps

So I have a rooted BND-L24 that I uninstalled a couple of system apps from, including the Huawei Home app. My question is: if I could track down an apk of the Home app, is there any reason I couldn't just reinstall it as a system app?
I've tried doing this already and the app shows up as installed, but when I try to select it as my launcher it doesn't work. So I'm not sure if I just installed a version that isn't meant specifically for my phone, or if there's no way to really reverse what I did and I'll just have to wait until firmware is released. Any info is appreciated.

Answered..
mjtschmid said:
So I have a rooted BND-L24 that I uninstalled a couple of system apps from, including the Huawei Home app. My question is: if I could track down an apk of the Home app, is there any reason I couldn't just reinstall it as a system app?
I've tried doing this already and the app shows up as installed, but when I try to select it as my launcher it doesn't work. So I'm not sure if I just installed a version that isn't meant specifically for my phone, or if there's no way to really reverse what I did and I'll just have to wait until firmware is released. Any info is appreciated.
Click to expand...
Click to collapse
IMO.. you've just answered your own question.
I'm at a loss as to why so many have rooted.. and there is no firmware yet available.. And, with all the updates that are coming.. backdoor bootloaders have to be sealed shut to open the front door.. and the Signed updates walk into a device to be installed.. (at least on the 1st days of the EMUI 8.0 / Oreo 8.0 rollout.)
I'm sure someone will make them available for a sideload in time..

RaiderWill said:
IMO.. you've just answered your own question.
I'm at a loss as to why so many have rooted.. and there is no firmware yet available.. And, with all the updates that are coming.. backdoor bootloaders have to be sealed shut to open the front door.. and the Signed updates walk into a device to be installed.. (at least on the 1st days of the EMUI 8.0 / Oreo 8.0 rollout.)
I'm sure someone will make them available for a sideload in time..
Click to expand...
Click to collapse
I'm pretty new to rooting, and it didn't even occur to me when I did it that I wouldn't have a stock image to reflash in case anything went wrong. In retrospect it was obviously a dumb idea. But oh well, I think of it all as a learning experience. I'll do my homework next time.
Anyways, my phone is still 98% functional at this point, just has one or two weird quirks from what I did, so I'm fine waiting it out. Thanks for the response!

No Problem Sir..
mjtschmid said:
I'm pretty new to rooting, and it didn't even occur to me when I did it that I wouldn't have a stock image to reflash in case anything went wrong. In retrospect it was obviously a dumb idea. But oh well, I think of it all as a learning experience. I'll do my homework next time.
Anyways, my phone is still 98% functional at this point, just has one or two weird quirks from what I did, so I'm fine waiting it out. Thanks for the response!
Click to expand...
Click to collapse
You're Quite Welcome Sir.
Don't feel bad... many rooted.. and all it means is... those of you that did, can only hope Huawei releases a Stock N Image that can be flashed prior to the rest of us receiving the Facial Unlock, EMUI 8.0 / Oreo 8.0 updates.. ( Not to mention Project Treble ) so they can receive them along with us.. or, someone or some app may allow them to sucessfully install the updates through a sideload.
There is nothing wrong with N running on the 7X... I Love my phone..
But I know that updates are going to be really, really cool as well !

Debating on rooting my Pixel 2XL, looking for seasoned android user's advice.

Hi all,
I am possibly interested in rooting my device. I have been rooting/rom'ing since back on my HTC Hero forever ago. Made a brief trip to iOS, and got into jailbreaking, but always missed the Android atmosphere. I am having issues with the battery on my device, and have debated factory resetting the device, and came across the forums about rooting.
I would just run a stock rom, with root, to be able to use Gravity box and Xposed. I am not super familiar with terminal/command line, so that part worries me a bit.
Anyone that is rooted, how does your device's battery last? Any major issues you notice? I use my camera for pictures of my family everyday, and don't want to risk anything that could compromise this feature.
Thanks in advance

Rooting doesn't hinder or damage or affect your battery directly
If you have enough reasons to root just root
I have plenty reasons to root that's why i did
Cheers ?
Sent from my Google Pixel 2 XL using XDA Labs

I've had lots of Android phones and tablets over the years, and every one was rooted at some point. Imo, rooting is not as critical as it used to be. Back in the early days of Android, rooting was the only way to get certain features that were later incorporated into Android. As Android matured, rooting became less important unless you needed a specific function or app. Rooting is still required for stuff like Titanium Backup, AdAway, Viper4Android, etc, because those need access to system-level files, which is impossible without root permissions.
Ask yourself what do you plan to do with root access? If you have a specific need for root, then go for it. Obviously you are not new to the game, and the procedure for rooting Pixel 2 is brain-dead simple compared to what you did for HTC Hero. However, if you don't have a specific need or plan, then it is not worth messing with imo. The Pixel 2 is an absolute beast out of the box. Root tweaks won't get you significantly better performance. I am rooted and use Sysconfig patcher (a Magisk module) to allow doze for Google Play Services for a very small gain in battery life. But I wouldn't root just for that. Monthly updates are a little more hassle if you are rooted, but if you get that far then you should be able to flash updates too.

AwkwardUberHero said:
Hi all,
I am possibly interested in rooting my device. I have been rooting/rom'ing since back on my HTC Hero forever ago. Made a brief trip to iOS, and got into jailbreaking, but always missed the Android atmosphere. I am having issues with the battery on my device, and have debated factory resetting the device, and came across the forums about rooting.
I would just run a stock rom, with root, to be able to use Gravity box and Xposed. I am not super familiar with terminal/command line, so that part worries me a bit.
Anyone that is rooted, how does your device's battery last? Any major issues you notice? I use my camera for pictures of my family everyday, and don't want to risk anything that could compromise this feature.
Thanks in advance
Click to expand...
Click to collapse
I too am a stock rom + root user. My battery life is outstanding for my usage patterns, usually 8-12 hours of SOT. As far as rooting, only you can answer that. Personally, I love it!! I like using dark themes, AdAway, TiBu, and the ability to use custom kernel tweaks. Having said all that, I haven't noticed any decrease in performance with day to day usage that you would likely use. So, if you ask me....root that sucker! ????

Badger50 said:
I too am a stock rom + root user. My battery life is outstanding for my usage patterns, usually 8-12 hours of SOT. As far as rooting, only you can answer that. Personally, I love it!! I like using dark themes, AdAway, TiBu, and the ability to use custom kernel tweaks. Having said all that, I haven't noticed any decrease in performance with day to day usage that you would likely use. So, if you ask me....root that sucker!
Click to expand...
Click to collapse
Seeing your input on this, Badger, makes me want to do it. Granted, not having rooted in over four years or so, I feel like I am missing a wealth of knowledge on this subject. I may give it a shot later today and see what happens. The only thing that worries me is installing the updates that come out each month. Do you do those monthly?

AwkwardUberHero said:
Seeing your input on this, Badger, makes me want to do it. Granted, not having rooted in over four years or so, I feel like I am missing a wealth of knowledge on this subject. I may give it a shot later today and see what happens. The only thing that worries me is installing the updates that come out each month. Do you do those monthly?
Click to expand...
Click to collapse
Oh I absolutely do the monthly updates using fastboot to install the factory images. It's actually very easy once you get the hang of it. You can look over my personal guide if you'd like so you have an idea of what to do :good:

Here's some more info for you to read as well :good:
https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418

Badger50 said:
Oh I absolutely do the monthly updates using fastboot to install the factory images. It's actually very easy once you get the hang of it. You can look over my personal guide if you'd like so you have an idea of what to do :good:
Click to expand...
Click to collapse
Do you really need to remove the lock screen password? I flashed the OTA (using this method: https://forum.xda-developers.com/pixel-2-xl/how-to/how-to-applying-monthly-security-t3750234), and I had no issue entering the PIN from within TWRP (twrp-3.2.1-2).

And don't forget that rooting is a XDA rush!

uofirob said:
Do you really need to remove the lock screen password? I flashed the OTA (using this method: https://forum.xda-developers.com/pixel-2-xl/how-to/how-to-applying-monthly-security-t3750234), and I had no issue entering the PIN from within TWRP (twrp-3.2.1-2).
Click to expand...
Click to collapse
Just my personal preference really. I just don't take chances with twrp if I don't have to :good:

sublimaze said:
rooting Pixel 2 is brain-dead simple compared to what you did for HTC Hero.
Click to expand...
Click to collapse
I never rooted my Hero but did completely unlock my HTC 4G LTE(S-off???). Dear lord was that a nightmare. I think back then it actually required a tool(Dirty Racoon???), only certain ROM's would boot on certain bootloaders, etc. I don't miss those days lol.

AndrasLOHF said:
I never rooted my Hero but did completely unlock my HTC 4G LTE(S-off???). Dear lord was that a nightmare. I think back then it actually required a tool(Dirty Racoon???). I don't miss those days.
Click to expand...
Click to collapse
I did root the HTC Hermes (win5) which was a trip!

AwkwardUberHero said:
Seeing your input on this, Badger, makes me want to do it. Granted, not having rooted in over four years or so, I feel like I am missing a wealth of knowledge on this subject. I may give it a shot later today and see what happens. The only thing that worries me is installing the updates that come out each month. Do you do those monthly?
Click to expand...
Click to collapse
While the 2 XL is a great phone even without root, I think there is just too much fun, experimenting, and customization to miss if not rooted. But this is a personal choice and you have to decide if you really want a specific battery icon, or any other custom feature.
You been given links to some steps and guides which are very good references. Since you said it's been four years since you rooted, I'm throwing in my guide as well
I am not a technical kinda guy, and sometimes the little details are what trip me up, so I crafted this initially for myself needing to be reminded of each step.
It is very detailed, step by step with tips and links and everything needed in one place. It certainly isn't the final authority for sure, but I've used it dozen and dozens of times with no issues. You can always default to the guide or other references if something isn't clear.
Take the plunge, I think you'll be very glad you did. In my opinion, root makes a great device an excellent device

@Az Biker @Badger50 I will be trying this on a Mac. Anyone happen to have steps for a Mac?
Thanks again for everything!

Mac instructions are in the op of the thread badger posted#7

galaxys said:
Mac instructions are in the op of the thread badger posted#7
Click to expand...
Click to collapse
Thanks! Totally overlooked that.

Badger50 said:
Oh I absolutely do the monthly updates using fastboot to install the factory images. It's actually very easy once you get the hang of it. You can look over my personal guide if you'd like so you have an idea of what to do :good:
Click to expand...
Click to collapse
Hey badger, thanks for these steps. Debating on trying this tomorrow. Do you have the actual rooting directions as well for a Mac? Tried looking in YouTube but could only find windows.
Thanks again in advance.

AwkwardUberHero said:
Hey badger, thanks for these steps. Debating on trying this tomorrow. Do you have the actual rooting directions as well for a Mac? Tried looking in YouTube but could only find windows.
Thanks again in advance.
Click to expand...
Click to collapse
First you'll need to enable developer options by tapping on the build number 7 times in settings/system/about phone. Then enable OEM unlocking and USB debugging. You'll need adb/sdk installed on your Mac, then you'll need to unlock your bootloader with the follow fastboot commands..
fastboot flashing unlock....
And
fastboot flashing unlock_critical...
You have to have magisk 16.3 and the twrp installer zip in your internal storage.
Then you'll need to fastboot the twrp.img with the Mac specific prefix command (which I don't know), but the command is...fastboot boot twrpxxxx.img
That'll boot you into twrp, then hit install, and navigate to where your twrp installer and magisk zips are. Flash twrp, followed by magisk, reboot, and you should be rooted.

Badger50 said:
First you'll need to enable developer options by tapping on the build number 7 times in settings/system/about phone. Then enable OEM unlocking and USB debugging. You'll need adb/sdk installed on your Mac, then you'll need to unlock your bootloader with the follow fastboot commands..
fastboot flashing unlock....
And
fastboot flashing unlock_critical...
You have to have magisk 16.3 and the twrp installer zip in your internal storage.
Then you'll need to fastboot the twrp.img with the Mac specific prefix command (which I don't know), but the command is...fastboot boot twrpxxxx.img
That'll boot you into twrp, then hit install, and navigate to where your twrp installer and magisk zips are. Flash twrp, followed by magisk, reboot, and you should be rooted.
Click to expand...
Click to collapse
Awesome. Thank you. I was messing with adb a bit today, enabling immersive mode and what not. I think that I can follow these steps.

Unrooting S20 Plus

Hi all
Hope this is the correct area...
My hubby bought me a S20 plus for my birthday through a local dealer.
I noticed a few issues like not being able to use biometrics or install certain apps.
I've since found out the phone has been rooted.
I've tried to do a factory reset, but this hasn't helped.
I've downloaded root checker and it confirms the phone is rooted. I've downloaded SuperSU yet is won't work as ver 2.82 claims it's for an older Version of Android.
I've downloaded solid explorer to delete the root access files such as Busybox and SU however I cannot find these files in the system folder or the system/bin folder.
Can anyone advise on how I can unroot my phone? I am unable to install certain needed apps due to this.
Phone details below. Sorry am unable to upload pics.
UI Version = 1
Android Version = 10
Let me know if other info is needed.
I've even tried calling the Samsung Center and they are unable to assist...
Thanks all
Lee

Lee KZN said:
Hi all
Hope this is the correct area...
My hubby bought me a S20 plus for my birthday through a local dealer.
I noticed a few issues like not being able to use biometrics or install certain apps.
I've since found out the phone has been rooted.
I've tried to do a factory reset, but this hasn't helped.
I've downloaded root checker and it confirms the phone is rooted. I've downloaded SuperSU yet is won't work as ver 2.82 claims it's for an older Version of Android.
I've downloaded solid explorer to delete the root access files such as Busybox and SU however I cannot find these files in the system folder or the system/bin folder.
Can anyone advise on how I can unroot my phone? I am unable to install certain needed apps due to this.
Phone details below. Sorry am unable to upload pics.
UI Version = 1
Android Version = 10
Let me know if other info is needed.
I've even tried calling the Samsung Center and they are unable to assist...
Thanks all
Lee
Click to expand...
Click to collapse
You will need to get hold of the stock firmware from somewhere like Sammobile and flash back to stock using ODIN. There's tons of guides knocking about on here for the step by step. The damage is done though as far as any Knox related features go, it's like a fuse that blows when you root and you can never fix that.
Having said that, biometrics should have never been affected by rooting so that's a bit unusual. Flash stock and set up from scratch then go from there, could be faulty also

Thanks for the guidance Dave. I'll search the forums for the steps.
For clarity, when I say biometrics didn't work, it works allow me to record etc, but when I tried to enable it, like on my banking app, it wouldn't allow me. This is how I eventually figured out my phone was rooted. While I know the benefits of being rooted, a normal everyday user like myself, certainly won't benefit from it.
I've had a Samsung my entire life, and always saw the secured by knox logo... When you say damage has been done, does this mean that all my security in the device, such as my banking details etc, may be compromised?
Jees. I hope not. As this would really freak me out...

Ok so Finding the firmware wasn't to difficult. Sanmobile quite easy to navigate.
Just a query please... My phone base band version lists g985fxxu1atb2 however the closest I could find to this is G985FXXU1ATBM
Is this ok or does it have to be the exact same description?
Shoo. Lol. Really hope I'm going to be able to get this right **insert nervous smile emoticon here**

Lee KZN said:
Ok so Finding the firmware wasn't to difficult. Sanmobile quite easy to navigate.
Just a query please... My phone base band version lists g985fxxu1atb2 however the closest I could find to this is G985FXXU1ATBM
Is this ok or does it have to be the exact same description?
Shoo. Lol. Really hope I'm going to be able to get this right **insert nervous smile emoticon here**
Click to expand...
Click to collapse
The last letters are the region/operator of the Rom. Not necessarily has to be the exact description, the really important are the first that indicate model number.

Ok. So have downloaded Odin and am busy downloading the flash firmware.
May I please be so bold as to ask someone on here to please share a link tot he step by step guide that I will need to follow in order to flash my phone back to the original boot thingie :silly::silly::silly:
I have tried to search but seem to only come up with a nexus thread with no mention of Odin.
~Sorry to ask, but little overwhelmed LOL and want to make sure I do this properly and not screw up my phone.
REAL noob here, so apologies if I come across lazy and getting others to do the work, but am really grateful for the help.
Maybe I'm searching incorrectly???

I found this somehow....
Is this it?
https://forum.xda-developers.com/galaxy-s20/how-to/howto-root-s20-series-upgrade-firmware-t4079353
**fingers crossed**

Can you unlock your phone with biometrics? Im guessing only the banking apps don't work because it's rooted. If i remember correctly most banking apps and maybe Google pay(not sure about that) stop working after rooting because the phone is "compromised" and it's not safe. You have to hide your root status from these apps and they will work properly then. Maybe someone else can help you with that because i do not remember how to do it.

Hi Marto
Yes, biometrics does work, although not really good. But that's probably due to the hectic screen protector.
Correctly so, it's mostly the banking / payment apps that won't work, and I can't check or download any software updates... Although I belive this can also be done manually....
But wow, there's an app that hides the root status? That might be a whole lot easier than re flashing. Truthfully I'm Sh!tting myself at the thought of attempting this ????

Hi Marto
Yes, biometrics does work, although not really good. But that's probably due to the hectic screen protector.
Correctly so, it's mostly the banking / payment apps that won't work, and I can't check or download any software updates... Although I belive this can also be done manually....
But wow, there's an app that hides the root status? That might be a whole lot easier than re flashing. Truthfully I'm Sh!tting myself at the thought of attempting this ????

if the phone was bought as new, go back to the dealer and demand a new one that is not rooted.
could also be that your husband rooted the phone and installed software that keep tabs on what you do.

Question All in one tool in the works?

I really hate asking this type of question as it makes me sound like a choosy beggar, but is there an all in one tool in the works for unlocking/rooting/flashing/etc? As I grow older, I desire rooting and tinkering, however I also value my free time a lot more lately (can't have both, right?).
Apologies if this is a silly question, however I thought I'd ask anyway! Thanks!

CacheOnlyPlease said:
I really hate asking this type of question as it makes me sound like a choosy beggar, but is there an all in one tool in the works for unlocking/rooting/flashing/etc? As I grow older, I desire rooting and tinkering, however I also value my free time a lot more lately (can't have both, right?).
Apologies if this is a silly question, however I thought I'd ask anyway! Thanks!
Click to expand...
Click to collapse
As far as I know, only the original Pixel 1 has an all-in-one tool* ("click button, wait, have fun - even though the P1 tool only came years after release!"), it has always been the culmination of a couple ADB steps/commands in a certain order, plus some manual flashing/magisk file creation incl. copying a couple files from your phone to your PC or vice versa.
Especially since Google changed alot of stuff with Android 11 and Android 12, it's a bit more complicated to root since the days of the original Pixel.
That doesn't mean that there can be no all-in-one root tool here, but as of now we have none and I don't see how one could be created in the foreseeable future.
*https://forum.xda-developers.com/t/...ck-twrp-factory-image-stock-recovery.3730227/

Morgrain said:
As far as I know, only the original Pixel 1 has an all-in-one tool* ("click button, wait, have fun - even though the P1 tool only came years after release!"), it has always been the culmination of a couple ADB steps/commands in a certain order, plus some manual flashing/magisk file creation incl. copying a couple files from your phone to your PC or vice versa.
Especially since Google changed alot of stuff with Android 11 and Android 12, it's a bit more complicated to root since the days of the original Pixel.
That doesn't mean that there can be no all-in-one root tool here, but as of now we have none and I don't see how one could be created in the foreseeable future.
*https://forum.xda-developers.com/t/...ck-twrp-factory-image-stock-recovery.3730227/
Click to expand...
Click to collapse
For sure, that's actually the All in One tool that I remember using with my Oneplus 7 Pro. This is my first Pixel phone (does the Nexus 6P count?) so I wasn't sure if developers would be all over it, or if Google has made things more complicated over the past couple of years. Either way I appreciate the reply and will probably dive into unlocking/rooting over the holiday weekend.

CacheOnlyPlease said:
For sure, that's actually the All in One tool that I remember using with my Oneplus 7 Pro. This is my first Pixel phone (does the Nexus 6P count?) so I wasn't sure if developers would be all over it, or if Google has made things more complicated over the past couple of years. Either way I appreciate the reply and will probably dive into unlocking/rooting over the holiday weekend.
Click to expand...
Click to collapse
If you want to read a bit about complication, take a search engine and find out what
Android 11 scoped storage
Android 12 Dm-verity (device-mapper-verity)*
Android 12 Vbmeta verification**
SafetyNet Android
Android Hardware Attestation
means.
*is a method by which an image on block devices (the underlying storage layer of the file system) can be checked to determine if it matches an expected configuration, using a cryptographic hash tree. If the hash doesn't match, dm-verity prevents the stored code from loading.
**is the other half of this - it provides a cryptographically signed reference hash which is used to verify the integrity of /boot, /system, and /vendor partitions. The vbmeta image is only used to verify /boot, while vbmeta-system is used to verify /system.
Click to expand...
Click to collapse
Google has been actively working - for a couple of years now - at making the modding/rooting communities life harder. We have always found a workaround, some require work (spoofing device ID, forcing software attestation, et cetera) or don't work that well at all, but it's a constant struggle.
Every firmware update is a small struggle and you got to pray to the man above that your device will still boot up, even if you have those pesky magisk modules disabled.

Morgrain said:
Google has been actively working - for a couple of years now - at making the modding/rooting communities life harder. We have always found a workaround, some require work (spoofing device ID, forcing software attestation, et cetera) or don't work that well at all, but it's a constant struggle.
Click to expand...
Click to collapse
I think Google's goal was to make our devices more secure, not making modding/rooting harder.

CacheOnlyPlease said:
I really hate asking this type of question as it makes me sound like a choosy beggar, but is there an all in one tool in the works for unlocking/rooting/flashing/etc? As I grow older, I desire rooting and tinkering, however I also value my free time a lot more lately (can't have both, right?).
Apologies if this is a silly question, however I thought I'd ask anyway! Thanks!
Click to expand...
Click to collapse
Not sure if this fits the bill of what you're looking for
Android Flash Tool

Perhaps this
Android Dollhouse (Flashtool) | TESTERS REQUIRED
Android Dollhouse The Definitive Android Flashtool. This is the support thread for Pixel 6 Pro. If you have another device, please check the other threads: Pixel 2XL: Support Thread Pixel 6: Support Thread I'm releasing the first user-facing...
forum.xda-developers.com

Az Biker said:
Not sure if this fits the bill of what you're looking for
Android Flash Tool
Click to expand...
Click to collapse
Sort of. Like I mentioned, I haven't dove into the details yet of rooting my Pixel 6 Pro yet, however can this tool you linked get me out of a potentially sticky situation if I ever need to load the stock firmware (ROM) onto it? That's really my biggest concern is messing something up. If I have a tool handy to get me back to stock, even if it wipes the whole phone, then I'm much more likely to dive in, you know.

For an all-in-one tool... what's wrong with fastboot?

CacheOnlyPlease said:
Sort of. Like I mentioned, I haven't dove into the details yet of rooting my Pixel 6 Pro yet, however can this tool you linked get me out of a potentially sticky situation if I ever need to load the stock firmware (ROM) onto it? That's really my biggest concern is messing something up. If I have a tool handy to get me back to stock, even if it wipes the whole phone, then I'm much more likely to dive in, you know.
Click to expand...
Click to collapse
If you haven't already looked them over, check the 6 PRO link in my sig, Step by step directions, pretty much each and every detail to make it easy for people like me who aren't rooting gurus.
Fastboot is the tool to pull you back from the abyss should you screw the pooch. Plenty of places you can find commands to help you out in a pinch, usually bringing you back to a factory fresh image.
Fastboot, update, and root a few times and it'll become much less concerning and tedious.