It seems like all custom roms include root. I'm trying to get around SafetyNet so I'd like to find one that doesn't. I currently have CyanogenMod 13 with virtual repartition version of TWRP. Are there ROMs like this? I'm currently reading through the development forum but most don't say one way or the other, probably because they include root.
If I can't find one, are there some that can be unrooted? I don't think CyanogenMod falls into this category. I can try to hide root if nothing else and have done a lot of reading on that using SUhide, Xposed, Root Switch but I think it would be a lot easier if there was a stock-ish kit kat or higher ROM I could use and unroot.
Thanks!
Depending on what you need to pass SafetyNet for, I'd say you are probably out of luck on the S2.
The last official ROM (from Samsung) for the Skyrocket was Jelly Bean (4.1.2), which is too old. Unfortunately, I don't know of any third-party ROM beyond that which doesn't come with root support pre-installed, and given the S2's curious bootloader configuration, it might not pass SafetyNet even if you could find one. Then, there is the minor fact that the S2 is old enough that it might be not be approved by Google even if you could get past all the other issues.
If you really need this, it might be time to consider an upgrade. However, if you do manage to get it to work, that would be a pretty cool find for this old phone.
Related
Hello all, I am relatively new to the android rooting scene. I have looked into it before but always became discouraged by the amount of different informaton from different sources. I am a little bit familiar with flashing processes as I used to install CFW onto Sony PSP and PS3 devices. However there's a lot of new terms that I am soaking in and trying to figure out what it all means when it comes to phone rooting. I am currently using a Sprint Galaxy S5 Sport running Lollipop 5.0, with build number, "LRX21T.PVPU2BOH1" and Kernel "3.4.0-4445742 August 6, 2015". I've been looking around and every time I think I find a reliable source for rooting I see a disclaimer saying only works with certain build numbers, and mine doesn't seem to be any of the builds I have seen. A Google search of my build brings a total of 5 searches wit no information regarding it. Anyways I am looking to successfully root my device, install a working recovery mode, and if possible, install a ROM. I have searched through threads and scrounge up some information about the SM-G860P but not enough for me to go through with the process with 100% certainty of success. I also hope that this thread can be useful to other SM-G860P users and a one stop shop for all the files needed to safely root, backup, and restore files. Basically, I know it can be rooted using Odin and CFAR on Lollipop 5.0. But the steps after that I am unsure. Do I install TWRP, CRM, what ROMS can I install, what kernel do I need. Thanks in advance to any developers or members who can provide all the proper links to attain my goal.
I have a very similar build. I have successfully put on root, and CWM recovery, but, any attempts at custom roms have failed (assuming due to kernel), and I am unable to get tethering working, despite having root.
Followed http://forum.xda-developers.com/sprint-galaxy-s5/development/recovery-cwm-s5-sport-sm-g680p-t2907945 for recovery.
I rooted following something like: http://www.android.gs/root-sprint-galaxy-s5-on-android-5-0-lollipop-os/. The key was using the auto root, then flashing the update via CWM. Had to make sure CWM was installed, as flashing using stock recovery caused issues.
Tried to flash CM12 from:
http://forum.xda-developers.com/sprint-galaxy-s5/development/rom-adulterated-cm12-5-0-2-t2987665
But ended up in a boot loop.
I'm also scared to put xposed framework on, since most saying need to use a custom rom or else phone will bootloop.
Using most of the methods to tether, (like adb settings global or sqlite), tether_dun_required keeps resetting back to 1 after turning on tethering, so, I still haven't found a solution to that. I'd love to hear from anyone who's got tethering working on SM-G860P with lollipop.
Hi All,
I have a two Relays that have served me well, and I enjoyed having them, but the time has come to pass them on to someone else. Before I do that, I'd like to update them to the most recent versions of stable-release software that is available for them.
For Cyanogen, I have:
cm-11-20150831 (this is stable)
cm-11-20160523 (this is a nightly build)
For recovery I have:
philz touch 6.48.4
I'd like to replace Philz with a newer TWRP, but the Relay is no longer listed on the TWRP website. I'm also wondering if there was ever a stable CM release newer than the one I have.
Does anyone have sources for the above?
Thanks.
Is there any one still developing for this device? If so, is it possible to get Android Go on it.. might just breathe new life into it and bring it upto date..
mrigancb said:
Is there any one still developing for this device? If so, is it possible to get Android Go on it.. might just breathe new life into it and bring it upto date..
Click to expand...
Click to collapse
Although I'm not a developer I have been working on my SGH T699 from T Mobile. You may already know of the JellyBean and before. Recently I've noticed new builds for the samsung Galaxy S Relay 4G like the Validus 5.0.2 or the Fat Toad. I haven't tried those yet I was trying for a higher version. With 8.0 Oreo it requires partitioning and I need to brush up on that. So I went lower to the 7.0 or the 7.1 Nougat. I started noticing a lot of broken or old links so I had to resort to fishing the internet for most of the packages apparently lost in XDA. I pretty much have all of them and was just starting to try a few out when I ran into problems like I want to keep using the keyboard and Wifi calling or a related Wifi issue. It also crashed, went into bootloop or even soft bricked within a few days. The Roms and packages I've found are highly unstable and I see many had flashing issues. So far I've been tricking my device into taking the flash and even then it doesn't hold long. I'd like 6.0 MarshMallow if I can, maybe 7.1 if they ever get stabler that'd be great. But so far the ROMs for the Galaxy S (relay) are fairly horrible to say the least. I get the impression these so-called developers aren't testing their ROM creations more than 5 minutes and then handing them off to noobs who may be very likely to brick their device trying to get it in and running, only to have it crash repetedly! Or worse, hard-bricked.
I like this device. I think I'll keep working on it.
Casper Young.
I'm not really a very advanced user, but always had rooted devices and two that I flashed Custom Roms. This is my first Samsung, finding Touchwiz to be very different from what I used before.
I bought the S7 (930F) and had the news that it was going to be updated to Oreo, so I decided waiting for the update before tinkering with it.. But the update never came. Finally this month Samsung released the update for my region, so I would like to know which would be the best way for me to start finally using my phone that I bought for over 2 months!
My phone is still with Nougat, is it better for me to get the OTA or to flash the Firmware I downloaded from Sammobile? Any of these methods better than the other in preventing errors? I always found in PCs that a fresh clean install was better than an update, but with mobiles I don't have the experience to say.
My main objective is to experiment before doing a debloat as I'm still not sure what might be useful for me on Samsung's bloat (you are welcome to point me what is useful and what is not).
I did see that some of the Customs ROMS have different camera apps and some people were complaining about this, I particularly liked the S7 camera app and the Pro option, that's what holds me back in flashing a Custom ROM atm.
I would like to Root and I find Unlocked Bootloader to be useful to have Xposed Framework and other things that I can do having it.
As I'm a relative newbie, what would you guys recommend me doing? Please help
tl;dr: I want to have Oreo, be able to debloat, want to root and unlock bootloader, not sure about Custom Rom.
Lineage if you want basic and simple (sort of like stock Android). Resurrection Remix if you're a customisation nut (not a slam... I use RR).
If you wonna full samsung u need flash base firmawre custom roms only 8.0 android
If you dnt need samsung integration (pulsometr doesnt work) you can flash 8.1 roms try cosmic os or Lineage 15
By all means, read @Neffy27 's FAQ if you are starting out. even as a refresher for stuff you may have forgotten.
-But do think a bit about what you are doing:
-Do not modify your phone unless you are willing to toss it into the trash, as that could well be the result, no matter how well planned.
-Always have a spare on hand. I used my old Moto G3 when my MZP died suddenly. Worked just fine. You know, things really haven't changed all that much since Gingerbread...
-If you are going to be getting the latest OTA stuff by doing a full flash you might want to reflect on just how much, or little, you would gain. We all like to think that if we have the latest security patch we are somehow more safe, though I don't believe I have ever heard of a phone being affected by something just because it is not on the latest patch. I was running my old Moto z play on an aug '18 (if I remember correctly) patch with no problems up until a few weeks ago when it was done in by an expanding battery envelope which cracked the display. Consider, also, that many of the custom roms that are available are not updated at all - it takes a ton of work to try to get/keep a custom ROM current, AND working! Yet you never hear of viruses or the like.
- Be aware that if you modify ANYTHING on your phone, even as little as a new boot logo to cover up the unlocked bootloader message, you will prevent your phone from taking any further OTA updates. Some mods, like adding TWRP, may still allow it to try to download and install an OTA, but when it reboots to finish that install, it will fail since it needs to re-boot through stock recovery to complete. And it will continue offering you that update.
- There is a difference between the partition structure in our phones on 8.x, and those on 9. 9 is not full Treble, only a "partial" Treble, and really only the addition of a second set of partitions which OTA updates can use to update the system - instead of modifying the single partition set, it modifies the other (a or b) set and boots to that on update completion. If it fails it can always boot the other set. Theoretically! Makes it safer than the old way of doing OTA updates, but this may cause problems if you try to flash a 2 partition set phone with a single partition set ROM. I don't believe anyone has run any experiments on this, so YOU, when you flash things without thinking about the situation, may get an unusable phone. I do not know the answer here. If you read these forums which detail other's problems, you may trod a bit more hesitantly!
-The idea here is to have fun, and sometimes to experiment with new things. To a newbie, losing the use of a $200 phone can be a tough life lesson. Let's help them out by helping them to be cautious!
Agreed. I've been running stock with January 2018 patch, TWRP installed and Magisk for root and successful safety net bypass.
I'm looking to see if running Lineage will help streamline any update processes. It looks like they have their own recovery too.
Maintaining root has become a pain in my ass the past few years.
Sent from my moto x4 using Tapatalk
SR3TLAW said:
Agreed. I've been running stock with January 2018 patch, TWRP installed and Magisk for root and successful safety net bypass.
I'm looking to see if running Lineage will help streamline any update processes. It looks like they have their own recovery too.
Maintaining root has become a pain in my ass the past few years.
Sent from my moto x4 using Tapatalk
Click to expand...
Click to collapse
I would be careful about lineage as folks don't seem to be able to get back to stock from it.
I agree about maintaining root. I will likely just stay on stock with this one.
bruh, I regret updating my samsung phone, Android 13 on the A53 is not good, the battery is wasteful and many applications don't use, which is a bad user experience. I've tried debloating and it's better but it's still good on Android 12 it turns out, yep I wanted to downgrade it was discussed before some said it didn't work. before I had a Samsung A10, I also had a custom ROM. many say you can't if the binaries are different, but after I try, I can flash it with other binaries. I want to try but with consideration of success. in download mode it says custom binary which I think can use any binary.