First of all I'd like to say that I'm sorry if I'm posting this in the wrong place.
I currently have the S5 but I'm in need of an upgrade so I was considering buying the S7 tomorrow. Before I buy a phone I like to know how to root it so I can root it as soon as I take it out of the box. The reason I'm writing this is because I've found multiple different rooting methods for the S7 and don't know which one I should use. I'm wondering if anybody could provide me with a link to a guide that will work for rooting the S7. I live in Canada so the model number of my S7 will be SM-G930w8
Also, how do I turn on/off root access on TouchWiz? I have an S5 but it's not running TouchWiz. I'm running CyanogenMod on it. In CyanogenMod there's an option to turn root on and off in the developer options in settings. I know that this option isn't available on TouchWiz roms, only AOSP roms. I'm a huge Snapchat user and Snapchat doesn't allow you to sign in when rooted so if I ever get logged out or re install the app I need the ability to disable root temporarily to sign back in so how do you disable and re enable root on TouchWiz roms?
Thanks for taking the time to read this. Sorry for the long post, and again I'm really sorry if I'm posting this I'm the wrong place.
Hi. If you want to root and pass safety net (so as to be able to use apps lile Snapchat or Pokemon Go) you need to root using Magisk. Another option is to use SuperSu+SuHide but magisk is more mature and is open source so I would recommend you to use it instead.
Magisk installation is very straightforward: install TWRP, flash Magisk installer and you are good to go. Please note that after installing a custom recovery your data partition will need tp be formated (use the "wipe->Format Data" option pf TWRP and reboot to recovery BEFORE installing Magisk.
On a side note once you install a custom recovery the Knox flag will be set to 1 and there is no coming back. As a result all the knox protected apps won't work anymore, ex: S-Health app, Secure Folder and so on. You can solve the issue with SHealth by editing one line of the build.prop, changing the property "ro.config.tima" from 1 to 0.
Warning: once you flashed a custom recovery and/or custom kernel DO NOT turn off Developer Settings (particularly the option "Enable OEM unlock") otherwise you will be locked out of the phone the moment you reboot it and you will need to flash the stock rom again (using ODIN). it happened to me today because of an stupid mistake [emoji28]
Cheers
Sent from my SM-G930F using Tapatalk
coto39 said:
Warning: once you flashed a custom recovery and/or custom kernel DO NOT turn off Developer Settings (particularly the option "Enable OEM unlock") otherwise you will be locked out of the phone the moment you reboot it and you will need to flash the stock rom again (using ODIN).
Click to expand...
Click to collapse
I've just flashed SuperMan ROM today (NOT using ODIN), and the "Enable OEM unlock" option is no longer under Developer Options.
dandv said:
I've just flashed SuperMan ROM today (NOT using ODIN), and the "Enable OEM unlock" option is no longer under Developer Options.
Click to expand...
Click to collapse
The option should be there if your are using a custom rom based on the stock rom like the SuperMan ROM.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I think the first warning should be: Once you root a Samsung device, your warranty is gone, also once you flash a custom recovery your Knox gets tripped 0x1. With Knox 0x1 there is no way you can revert it back to 0x0.
Related
First of all, I am newb, kindly ignore silly replies till I am used to technical stuff, Very new to Android World.
I have upgraded to lollipop 5.0 properly from KitKat. Now planning to root my device to try more..
I have succesfully done following with guidance of http://forum.xda-developers.com/member.php?u=5375117 :
1. I am using following files as recommended, http://forum.xda-developers.com/showpost.php?p=58648567&postcount=297
Using odin 3.10
2. Followed instructions from this post http://forum.xda-developers.com/showpost.php?p=58732404&postcount=345
I used that CF method once and it ended up tripping my knox counter. So I will just stick to the su method I used.
Once you launch odin. Make sure only the Autoreboot and F.Reset time boxes are ticked on the left side of Odin.
Then head over to the right side,Tick the box just before AP and then navigate to where you've downloaded the CWM. select it.
Now boot your phone into download mode (press power+volume down+ home), connect it to the PC and once that part written ID COM on odin goes green, click on start and wait for odin to do its thing.
Upon completion, your phone will reboot.
Click to expand...
Click to collapse
Was able to complete this task properly, without any issues.
Now make sure you copy the super su zip file to your device storage then reboot into recovery (press power+volume up+home button) and flash the zip file.
Thats it. Your sm-n900 will be rooted.
Click to expand...
Click to collapse
After following the above method. I am getting "signature verification failed of entire file" continuously. I also retried after removing the battery and replacing it back. But getting the same error.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Tried removing battery + renamed the file to update.zip but nothing works.
I got another suggestion:
hat means the zip file is corrupted. Disable signature verification in CWM
Click to expand...
Click to collapse
But there is no way I can find an option to disable signature verification in CWM for NOTE 3 SM-N900
Looking for expert advice.
So far, being little more comforable with android compared to my DAY 1 here.
Regards,
You need custom recovery to flash that .zip file via recovery. Stock recovery requires certain signature in the file.
You can use the CF-Auto-Root to root your phone, you can find it in Original Development section. Requires Odin for that.
Someguyfromhell said:
You need custom recovery to flash that .zip file via recovery. Stock recovery requires certain signature in the file.
You can use the CF-Auto-Root to root your phone, you can find it in Original Development section. Requires Odin for that.
Click to expand...
Click to collapse
Dear sir,
Request you to kindly help me through step by step instructions.
I am a newb for sure but will never give up.
User helping me said no to go for cf-suto-root for some knox counter issues.
Kindly help what right file to download and go ahead with right stuff.
We have few more mobile to test everything. We keep getting
SwiftKey keyboard messed around many options SORRY
CF-Auto-Root is pretty much only method for Lollipop at the moment. Yes, it does trigger the KNOX Warranty Void flag though, look it up if you want to know what it means (voids warranty in certain regions apparently, definitely not in EU).
Instructions are in the first post of the CF-Auto-Root topic - http://forum.xda-developers.com/showthread.php?t=2466423
I can post better instructions tomorrow, no time today.
I followed the above method, phone rooted properly.
But now I end up with phone not booting.. due to some mistake.
http://forum.xda-developers.com/galaxy-note-3/help/unfortunately-applications-stopped-t3027814
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
good afternoon
I root my Samsung tablet t285m
someone knows how i try and root with vroot and kingorot and nothing
I need root please help
I come to this forum because they are the master of the android
[IMG="TABLET SM T-285 TABLET A"]
[/IMG]
please see my PM (private message) maybe set you in some direction maybe not...also need help from you if possible advice/guidance
thanks
needed root file
gencom said:
needed root file
Click to expand...
Click to collapse
http://forum.xda-developers.com/galaxy-tab-s/help/looking-to-direction-root-galaxy-tab-a6-t3390941
(T285M,....modified system image for debloat etc-tar.md5 fails on flash in odin-not sure if some signing is needed-have the system folder if anyone interested...took out some apps, added csc folder with some xmls for control on data on off auto for mms, added two fonts...nothing more than that)
also see page 14 here
http://forum.xda-developers.com/and...ng-tab-e-sm-sm-smnu-smp-t3302935/post66585078
I just got my T285 yesterday. Noticed that in Setting, App manager I can move some app to sdcard but after restart, the moved app disappear.
Sorry if I have mislead anyone.
Now I am also facing memory shortage with this 8G device.
I have lost all hope for root on the SM-T285. Why such a low profile device gets a locked down bootloader annoys me.
However I'm trying to customize its system.img, I'm stuck though as Heimdall fails at 3% upload everytime I try to use a repacked system.img file. Flashing the original image works fine though so it could just be in the way that I repackage the image. tune2fs shows some difference which I am still trying to sort out.
I'm willing to help if there are things that I can try.
jaritico said:
i found this on web, seems fake but, uses a beta root file of cf auto root webpage:
HOW TO ROOT GALAXY TAB A 7.0 (2016)
Note: This is a developing story. As far, we have found only one way to root your phone. But if someone invent more tricks of rooting in future, we will try to share with you.
You can install Chainfire’s SuperSU manually using a custom recovery such as TWRP (In this method we are showing how to install SuperSU.zip file with TWRP). If you are interested, check details below but take a backup of your device’s data first. This method should work with any variant of tab including SM-T280 (Wi-Fi only) and SM-T285 (4G/Wi-Fi)
Step One: Download Chainfire’s SuperSu.zip file.
Step Two: Copy the downloaded zip file to your device.
Step Three: Turn off your Samsung device and boot into recovery mode (boot device by pressing and holding down volume up, home, and power keys at the same time to enter in recovery mode).
Step Four: Take a backup, it is optional but important because if something happen bad in rooting, backup file will help you to restore previous state easily. So press ‘backup’ button, check all the boxes for backing up everything and then swipe to start the game.
Step Five: Once you have taken the backup file, press ‘install’ button, locate the SuperSu.zip file and confirm you want to install it.
Step Six: Reboot the device and your device is rooted.
Credits: http://lifeatsamsung.com/root-galaxy-tab-7-0-2016/
Click to expand...
Click to collapse
Yeah it's fake. To even be able to follow that, you need a custom recovery, but there is no way to install custom recovery right now with a locked bootloader.
It took me two days to find a solution to a locked FRP that I could bypass but not root. I found this solution to fix the following problems:
FRP lock
Google account lock
Downgrading rom
Root locked device
Flash custom recovery on a FRP locked or Activation Lock enabled
Can't sign in to Samsung account after factory reset
Cannot delete Samsung account
Cannot add Samsung account
Cannot disable Activation Lock
Activation Lock greyed out
Custom Binary (recovery) Blocked By R/L
Custom Binary Blocked By FRP Lock
Recovery is not Seandroid Enforcing
ODIN Complete(Write) operation failed.
Odin: Flash write failure
Solution:
Step 1: Download and install a "Combination file" for your device
I did a google search for mine, and came across a few Combination files for mine, some can be found here: https://www.mobileheadlines.net/download-samsung-combination-file/
Step 2: Flash the "Combination file" for your device
Flashing it with ODIN with result in an error so I used Z3X samsung to flash it:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The Z3X 29.5 Samsung Tool Pro with Loader tool can be downloaded from here: https://www.techeligible.com/2018/04/01/download-z3x-29-5-samsung-tool-pro/
* Remember to start the loader as admin in windows
Step 3: Start phone
The phone will start in factory mode, which will allow you to test every feature of the phone, as well as have access to settings.
Optional Step: Enable Developer tools and ADB (optional)
Easy to do, and you will get ADB
Optional Step: Unlock FRP using ADB
Plenty of methods around, I used Miracle box:
Optional Step: Flash any stock ROM you want
Should be easy using ODIN, but I did it with Z3X. You can flash ROM with Pit, without, one file, 4 files, downgrade/upgrade to your favorite ROM without hassle
Step: Root
Should be easy using ODIN, but I did it with Z3X:
Step: TWRP flash
Should be easy using ODIN, but I did it with Z3X:
Step: Custom rom install and kernel
Use TWRP
--Done using Samsung galaxy note 4 910U
Thanks and buying me a beer welcome
after 3 days of researching... Success at last
Kiwironic said:
after 3 days of researching... Success at last
Click to expand...
Click to collapse
you flashed a stock kitkat rom or a custom kk rom?
MystaMagoo said:
you flashed a stock kitkat rom or a custom kk rom?
Click to expand...
Click to collapse
I flashed only stock, but actually I skipped the kitkat part all together, jumped to Marshmallow 6.0.1 , the screenshot is on it
:good: okay
is the procedure same for samsung gear s3? where can i get the combination file for this. thank you in advance
Thread Closed.
Thanks
SacredDeviL666.
Hello ppl,
I have a few questions I would like answers to, I got the Poco X3 NFC recently and I was able to unlock the booloaded properly with the official method (waiting the 7 days), but when I think about the root process is njot entirely clear for me.
Is there a way to root the android device without installing the custom ROM?? os is that a must?
I heard some Bank applications will not run in rooted phones, how usual is this? and is there a way to know which apps come with this resticction?
seems like magiks is a good choice for rooting as it keeps the original boot.img in the device so the rooting checks are not failed. how better is this? than other methods?
I am also wondering if there a process for reviewing the custom ROMs available over the internet? I mean how safe are those in terms of malicious code?
And finally what are the best custom ROMS out there for the x3 NFC that you would recommend in case I go for the ROM flash route.
thanks in advanced for any details
You absolutely don't need a custom ROM to get root -- all you need is an unlocked bootloader, which apparently you already have, plus a custom recovery like TWRP or OrangeFox to be able to flash Magisk. Evrything else, IMMV...
Thx pnin ill check deeper in to magisk then
I have another question.. in order to backup my current stock phone's partitions do I have to flash TWRP first? or can I get the backup done some other way?
It's possible there's a way to do this with ADB ("platform tools") and a computer that I don't know about -- otherwise you absolutely have to flash TWRP/OrangeFox first...
I am on Indonesian stock rom. And removed these apps via debloat in magisk module. I think its quite enough. You dont need custom rom. Magisk can hide root. So no worries.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'm a De-bloater user myself -- but I wouldn't risk anything without a working custom recovery. Things tend to get pretty hairy as it is...
pnin said:
I'm a De-bloater user myself -- but I wouldn't risk anything without a working custom recovery. Things tend to get pretty hairy as it is...
Click to expand...
Click to collapse
yeah seems like RCS is very important... I have reinstalled it.
Hey thanks for all answers, so I manged to get mine rooted, the TWRP works but is not persistent, meaning you cant flash it, but can boot it, so I booted and installed magisk with it, I now have rooted x3 NFC, and passing the safety net scans all green.. the only thing is I debloat some apps like mi video and other mi-services.. but after some time they re-appeared... any advises on getting rid of them permanently?
pnin said:
It's possible there's a way to do this with ADB ("platform tools") and a computer that I don't know about -- otherwise you absolutely have to flash TWRP/OrangeFox first...
Click to expand...
Click to collapse
I found it, adb pull and the partition name, I took a 100gb image though so Is not easy to tamper with as it is too big, none the less I managed to complete the whole rooting process properly so I guess I can try again to backit up as it is.. but I can boot in to TWRP so I guess is not enirely needed.
Hi,
I have problem How can I roll back to Android 11 from 12 ROM.
I have DFE and root .
Please help me because my work apps don't work on A12.
as far i know there is no android 12 stock rom yet. perharps you are in a custom rom... if that is so.. you just need to flash stock rom with miflash tool and the androdi 11 stock rom version of your device (global, eu, china, etc...) but be careful with the *clean all *save user-data *clean all and lock scripts.... right now some apps detects the bootloader unlocked and maybe that's why your apps doesn't work. you also can try magisk (and magisk hide) to get your apps work again but topjhonwu (creator of magisk) have already drop support of "magisk hide" so is only matter of time for root also stop working
I don't I have rtn PC so I need do it in all in TWRP on phone .
also.. you can check if the rom you want to rollback does not brick ypur device with the "anti-rollback" system that xiaomi create...
use the cmd command "fastboot getvar anti" on fastboot mode, you will get a number (0,1,2,3,4) and check your rom that has the same or higher number....
for example:
if your device shows "anti: 2" you can only flash (trought miflash tool) roms with anti_ver_ : 2,3,4)
on the scripts of your stock rom "clean all *save user-data *clean all and lock you can check the anti rollback version of the rom by using notepad++ and looking something like this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
astronomy2021 said:
I don't I have rtn PC so I need do it in all in TWRP on phone .
Click to expand...
Click to collapse
again.. if you are in a custom rom.. you can flash android 11, but the fact that your apps wont work because you rooted your device has nothing to do with which version of android you flash... but if your apps detects that the bootloader is unlocked... you can only relocked again using the stock rom with the *clean all and lock script...
google tutorial on youtube.. there are plenty of them and in different languages
You don't understand my apps works on rooted device but not Android 12 I had few ROM like Arrow Os or PE and root and kernel but no problem now I try thee ROM of Android 12 and doesn't work at all.
astronomy2021 said:
You don't understand my apps works on rooted device but not Android 12 I had few ROM like Arrow Os or PE and root and kernel but no problem now I try thee ROM of Android 12 and doesn't work at all.
Click to expand...
Click to collapse
aahh, i get it now.... then just flash arrow os 11... but i think you are gonna loose data
astronomy2021 said:
I don't I have rtn PC so I need do it in all in TWRP on phone .
Click to expand...
Click to collapse
you dont have pc and dont have access to data
now that is a very tough situation
do you have SD card?
Your not encrypted right?
Just wipe super, data (NOT Internal, so media file is safe), cache.
Then flash the ROM + DFE.
You'll be okay and stay decrypted.
But if you're on encrypted internal, you need to format internal in TWRP (lose all data + media)
Also
Magisk isn't dead.
There's Magisk 24 with new root hide solution Zygisk.
.... and big problems with lost root and email certificates... i´m just trying to return to Magisk 23 because of massive problems with version 24 sharing this with some more users ...