Hello,
So many moons ago I was quite accustomed to flashing my old Galaxy S3 with custom firmware, so now I have an aging S6 and the latest official update is sh#!, so I am pondering my options for rooting / custom flashing. However, there seems to be a lot of varying info for the S6 out there, so I just want to get it straight before I flash it.
In the past I used ODIN, so happy to go down this path again. I've read that I need a custom boot kernel to avoid the non-boot issue caused by dm-verity. If I flash TWRP using ODIN, I assume this will then become non-bootable. But is it then simply a matter of flashing SuperSU via TWRP and it will replace the boot kernel and fix this issue, rooting and bypassing dm-verity? Is there a specific SuperSU image for the G920I I need to grab or is it just a matter of flashing the latest stable, like the one found here? https://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703
Also, in the past I ran SlimROM on my S3. Can anyone suggest the best stable custom ROM similar to Slim (i.e. quite vanilla with very little overhead / feature bloat) for my S6?
Thanks in advance!
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.
Good morning,
where can i find or how can i make a stock rom flashable via TWRP of stock firmware SM-G930F?
thanks
i want to know this same thing too if possible. previously owned S5 smg-900f which was good, but defo needs root access to unlock those missing things and remove the bloatware. S5 was simple to root but custom roms just caused problems so i found an almost stock one back then which worked great.
S7 edge smg-935f seems to be much more of a task.
i've tried various different methods already to try to get the s7 edge on root but it just isn't having it so far after about 20-25 attempts. different issues keep popping up.
*before you say it, yes it is the exynos not snapdragon version*
I need only because all the roms modded are for edge version and generate some problems on flat, so i want to flash a stock from TWRP keeping the advantage of use twrp for modding but remain stock... (i know that with odin i can flash stock an then mount TWRP..but i want a last chance when i made some troble with custom roms...)
bye
There is at least a way to make it from official stock firmware??
Hey guys,
Samsung Galaxy S4 GT-i9505 International
I was experimenting with LineageOS and SlimROM recently. Decided to go back to my stock ROM. Kies doesn't support restoring my phone in this way. I went on SamMobile, got what I thought was the correct ROM, flashed in via ODIN, and thought all was well.
Ran into problems with WiFi not turning on, then got an error when attempting to update OTA: 'The operating system on your device has been modified in an unauthorised way.' Both the Bootloader and in-OS device status show 'Custom'.
I have a couple of concerns:
Is this ROM potentially compromised or otherwise unsafe?
I've logged in to my Google, Reddit, Discord, etc, accounts on this new ROM. Are these accounts potentially at risk?
How can I find a reliable and trusted ROM for my device?
your phone has a custom recovery or modified bootloader some leftovers
something didn't get flashed from the official ROM in ODIN , maybe a reflash (could also fix wifi maybe)?
did you wipe/clear/format everything also before the ODIN flash sometimes helps for me.
my samsung shows Custom with official (Clean) rom but its to be expected , i have custom recovery TWRP. but i don't use OTA so i don't care its broken.
did you mind that it was custom when using LineageOS and SlimROM , it just wasn't displayed.
i suggest sticking with LOS > TOUCHWI(zzzZzz)
also you can fake system status to Official if you use Xposed touchwiz module
but i don't know if fixes the broken OTA. but it will show Official in your settings.
never had any problems.
hope this helps some.
LineageOS and SlimROM were (7.1.2) ? Official ROM version ? samsung also likes to make it difficult to downgrade sometimes (wifi,modem issues)
Thanks!
So you don't think I need to worry about my data being compromised?
I should mention I was getting a lot of CloudFlare screens while trying to access SamMobile to download this ROM, so I was concerned the file may have been compromised.
i prefer updato to SamMobile , but have used so many roms from both of those sites
they are both legit
SamMobile roms are clean no worries. site is good.
ive lost count how many different roms / models / versions i have flashed from there all perfect.
plus you can verify the MD5 checksum of the (exact) ROM with other sites , sources also. if you want even more proof
forceLaser said:
i prefer updato to SamMobile , but have used so many roms from both of those sites
they are both legit
SamMobile roms are clean no worries. site is good.
ive lost count how many different roms / models / versions i have flashed from there all perfect.
plus you can verify the MD5 checksum of the (exact) ROM with other sites , sources also. if you want even more proof
Click to expand...
Click to collapse
Cheers guys!
I may have screwed up and not formatted as cleanly as I should have before flashing the stock ROM. What's the recommended process for this?
FIXED!
I'm going to make a semi-educated guess as to what happened.
I figure that the first time I flashed the stock ROM after running SlimROM, I had to boot into the download mode/bootloader that was running alongside (or was a part of?) TWRP.
This meant that a little bit of TWRP couldn't be removed during the flash, because it was helping manage the flashing process.
So I went back into the now-stock bootloader and used ODIN to flash the stock ROM a second time, purging the last few traces of TWRP.
I'm now getting WiFi connectivity, OTA updates, and my Device Status has changed to Official. I'm so happy that it was my ****-up and not ROM file that had been messed with.
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
I've finally decided to reflash the original rom I flashed my zerofltexx with back in the day I got it because of a weird calling issue. To my suprise, a metric buttload of new roms that actually looked appealing, unlike back then, have sprung up. What caught my eye in the end was DotOS, specifically it's Android 9.0.0 iteration. Went through the standard flashing process via TWRP, and to my suprise, the proffessional-looking ROM has no system setting for enabling root capabilities.
Seen as I've been out of this game for a while, I do wonder, how does one root a custom firmware? I've tried towelroot, which never worked for me on any device and unsuprisingly didn't even here, and then I remembered about cf-autoroot, but seen as how the ZIPs are builds for presumably OFW Android 6.0, 7.0 and 7.1, I didn't try it, as to not risk bricking the device.
Can anybody help me with this or should I just flash a credible ROM? If so, do you have any recommendations? I'm looking for stability and reliability first and foremost.
Thank you.
Magisk
Download TWRP (https://twrp.me), Odin (https://samsungodin.com) and Magisk (https://magisk.me).
1) Flash TWRP 'without restarting' by Odin.
2) In TWRP flash Magisk.
3) Restart.